Project

General

Profile

« Previous | Next » 

Revision 4994a23f

Added by François ARMAND almost 7 years ago

Fixes #10698: Update server requirement with load test data

View differences:

10_installation/05_requirements/30_hardware_specifications.txt
A dedicated server is strongly recommended, either physical or virtual with at least one dedicated core.
Rudder Server runs on both 32 (if available) and 64 bit versions of every supported Operating System.
[NOTE]
====
Rudder does not fear big infrastructures. It is currently used in production in
infrastructure with more than *7000* nodes.
====
===== Memory
The required amount of RAM mainly depends on the number of managed nodes. A general rule for the minimal value is:
* less than 50 nodes: 2GB
* between 50 and 1000 nodes: 4GB
* more than 1000 nodes: 4GB + 1GB of RAM by 500 nodes above 1000.
* less than 50 nodes: 2 GB
* between 50 and 1000 nodes: 4 GB
* more than 1000 nodes: 4 GB + 1 GB of RAM by 500 nodes above 1000.
When managing more than 1000 nodes, we also recommend you to use a multiserver
installation for Rudder as described in chapter <<multiserver-rudder, Multiserver Rudder>>.
For large installations, you should also tune the amount of RAM given to:
When your server has more than 2 GB of RAM, you have to configure the RAM allocated
to the Java Virtual Machine as explained in the section
<<_configure_ram_allocated_to_jetty, about webapplication RAM configuration>>.
When your server has more than 4 GB, you may need to also tune the PostgresSQL
server, as explained in the <<_optimize_postgresql_server, Optimize PostgreSQL Server>>
section.
[TIP]
====
As an example, a Rudder server which manages 2600 nodes (with a lot of policies
checked) will need:
* the web application, as explained in the section
<<_configure_ram_allocated_to_jetty, about webapplication RAM configuration>>
* PostgresSQL, as explained in the <<_optimize_postgresql_server, Optimize PostgreSQL Server>> section
* A server with 8 GB of RAM,
* 4 GB of RAM will be allocated to the JVM.
In our load-tests, with such a configuration, the server is not stressed and
the user experience is good.
====
===== Disk
......
----
For example, a default installation with 500 nodes and an average of
50 Directives by node, should require between 14 GB and 38 GB of disk space for PostgreSQL.
50 Directives by node, should require between *14 GB and 38 GB* of disk space
for PostgreSQL.
Follow the <<_reports_retention, Reports Retention>> section to configure the
retention duration.
[WARNING]
====
Be careful to correctly size your */var* partition. Compliance data are growing
fast, and PostgreSQL doesn't like at all to encounter a write error because
the disk is full. It is also adviced to set-up your monitoring to check for
available space on that partition.
====
23_configuration_management/31_techniques.txt
include::../glossary/active-techniques.txt[]
[TIP]
==== Create new Techniques
====
The current version of Rudder has only an handful of *Techniques*. We are
aware that it considerably limits the use of the application, but we choose to
hold back other Techniques that did not, from our point of view, have the
sufficient quality. In the future, there will be some upgrades including more
Techniques.
====
[WARNING]
====
The creation of new Techniques is not covered by the Web interface. This
is an advanced task which is currently not covered by this guide.
====
The standard library only provides the most common Techniques. You can create
new Technique with the <<technique-editor, Technique Editor>>.

Also available in: Unified diff