You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
After doing some reading it seems like Nginx might perform better with static content and many concurrent users/requests. I believe Jira doesn't have many static content and we have ~200 users.
Does anyone have experience with replacing Apache+Jira with Nginx+Jira or with Nginx+Apache+Jira?
In case you do, why did you do it and was there any performance improvement?
I've seen this done on several servers, and the answer is a very clear "maybe". In a couple of places, the metrics came out at "negligble change", one place took a performance hit of around 30% on page loads, and another one saw a 30% improvement.
I think it's important to look at why you're doing it, and most importantly, what your internal support teams support better.