allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #8262 System configuration for production environment
Date Tue, 13 Nov 2018 15:26:24 GMT
Hi Vrinda,

The overall system requirements depend largely on how much traffic and how much data (repos,
tickets, etc) will be in the system.

* MongoDB - I would recommend having MongoDB on a separate server (and potentially as a replica
set, for failover).
* Web service - See for recommendations about the webserver:
 If you need to scale up further, you can have multiple servers running the allura web services,
with a load balancer in front.
* Solr - You can also have the solr server separate, and multiple of them if you want.
* Taskd - You should run multiple taskd processes.  They can be all on their own server, or
multiple servers, or shared with another server if there is enough ram/cpu for it.

To configure Allura for good performance, see [production-docker-example.ini](
 It is good to look through all of it, but lines 75-79 are particularly important for performance.



** [tickets:#8262] System configuration for production environment**

**Status:** open
**Milestone:** unreleased
**Created:** Mon Nov 12, 2018 11:22 AM UTC by Vrinda
**Last Updated:** Mon Nov 12, 2018 11:44 AM UTC
**Owner:** nobody

I am setting up a production server to host Allura platform. 

So I have some general questions before I start:
1. What is the expected system requirement/configuration for a production server to host Allura?
2. Are there any specific configurations that I need to do in Allura to get a good performance
when the load is high (for >100 users)?
3. Any other points that I need to be aware about?


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message