User story #4053
closed
Add a section in documentation about sizing of a Rudder server
Added by Nicolas PERRON about 11 years ago. Updated over 9 years ago.
Description
A chapter about the sizing of a Rudder server should be added. A new user will not be able to estimate the size required.
This issue concerns all versions of Rudder.
Updated by Ed DANIEL about 11 years ago
While we prepare the documentation here are a few guidelines to help new users get started:
CPU/VPU: At least 1 cpu core dedicated to Rudder.
32/64bit: your preference, Rudder Server is available on both 32 and 64 bit versions of every supported Operating System.
Memory: at least 1GB though 2GB is better. 4GB preferred if the server is managing other tasks.
Bandwidth: bandwidth utilisation is very small, it will rarely exceed 0.005% of bandwidth on a 10GB net, dependent on agent density which is usually 100%.
Local storage (deployment): Rudder will need about 300MB.
Local storage (logs): Every action taking place in the Rudder web interface and all agent logs are stored in the PostgreSQL database. If logs are localised it will be prudent to allow at least 5GB. When deploying to production with weekly log rotation then 5GB is sufficient for most cases though the number of reports that are generated and thus archived suggests at least 20GB+ will be required.
Postgres: it is worth optimizing this -> http://www.rudder-project.org/rudder-doc-2.7/rudder-doc.html#_server_optimization
As each and every site configuration is different these are very much guidelines. We will strive to provide greater clarity in the upcoming addition to our documentation based on this user request.
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.12 to 2.4.13
Updated by Matthieu CERDA almost 11 years ago
- Status changed from New to Discussion
- Assignee set to Nicolas CHARLES
- Target version changed from 2.4.13 to Ideas (not version specific)
I know that we now have a script to bench a Rudder server installation statistics, it might prove useful to use this to construct a "basic" idea of sizing.
Nicolas, what do you think about that ?
Updated by François ARMAND almost 11 years ago
- Status changed from Discussion to 15
- Assignee changed from Nicolas CHARLES to François ARMAND
Updated by François ARMAND almost 11 years ago
- Status changed from 15 to 10
- Assignee changed from François ARMAND to Jonathan CLARKE
Pull request here: https://github.com/Normation/rudder-doc/pull/49
Updated by François ARMAND almost 11 years ago
New pull request: https://github.com/Normation/rudder-doc/pull/50
Updated by François ARMAND almost 11 years ago
- Status changed from 10 to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:91343bd27202f950720bd2f640a087a2ee925123.
Updated by Anonymous almost 11 years ago
Applied in changeset commit:bdbebdd8bc48f9189fd8bc5055320ab2c3d46c3b.
Updated by Jonathan CLARKE almost 11 years ago
- Target version changed from Ideas (not version specific) to 2.6.11
This has been clarified in http://www.rudder-project.org/rudder-doc-2.9/rudder-doc.html#Server_supported_OS.
Updated by Vincent MEMBRÉ over 10 years ago
- Subject changed from Add advices about sizing of a Rudder server to Add a section in documentation about sizing of a Rudder server
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000077.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 30 to Rudder
- Category set to Documentation