Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,986
Community Members
 
Community Events
184
Community Groups

Pros and Cons for hosting Confluence on a separate App and DB Server vs. on Jira's App and DB server

Pros and Cons for hosting Confluence on a separate App and DB Server vs. on Jira's App and DB server. We've had some serious performance issues and were wondering what other's consider the best server hosting setup.

We currently have 4 servers. About 140 licensed Agents and 4000 customers. Also 330,000 issues and mainly use Jira for it's Service Desk project.

One server hosts Jira App Prod and Confluence App Prod

Second Server hosts Jira DB Prod and Confluence DB Prod

Third Server hosts Jira App Test and Confluence App Test

Forth Server hosts Jira DB Test and Confluence DB Test

1 comment

Peter-Dave Sheehan
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 19, 2019

Can't contribute to the performance pros and cons ... but I can share our setup.

We opted to isolate each app in prod. And combine them in Test.

We would have (for example)

  • 1 prod server with both Jira App and Jira DB.
  • 1 prod server with both Confl App and Confl DB
  • 1 test server with both Jira and Confl app & DB.

This way, we can perform maintenance on one app while leaving the other one untouched.

Except in very rare cases of bad runaway query from a plugin, the DB doesn't seem to put a big drain on the server resources.

Comment

Log in or Sign up to comment