Memory and Disk space requirements for one JON server and 80 remote agents

Latest response

Hi All,

Good Day..

We are going to build the new JON environment , Could you please let me know the memory and disk-space requirements for the following

  1. One JON server( this need to save and monitor the 80 agents statistics.)
  2. Oracle Database
  3. 80 JON agents (per each agent how much disk-space is required)

Please let me know your thoughts on this.

Thanks,
Kalli

Responses

Kalli,

Due to the uniqueness of each JBoss ON environment and your managed resource types and data collection patterns, sizing recommendations become very difficult.

I can only provide you some basic information as a starting point based on experience with other users. This information does not constitute a minimum requirement and is only a suggestion based on using the latest JBoss ON 3.3 release.

One JON server( this need to save and monitor the 80 agents statistics.)

4 GB of JVM heap for the JBoss ON server process and 2 GB of JVM heap for the JBoss ON storage node should be sufficient. Keep in mind that physical memory would need to provide a sufficient buffer and be able to handle operating system and shared library requirements outside of the JBoss ON components. In most cases 8 GB of physical memory is sufficient.

20 GB of disk space should be a good starting point. However, this assumes that JBoss ON storage node snapshots will be moved to external storage. If you plan to leave some snapshots in place, you probably want to allow for at least 10 GB of additional disk space per snapshot.

If you plan on separating the JBoss ON storage node data directory to a separate partition, you can split this 20 GB into 5 GB for your JBoss ON server installation and its necessary files and 15 GB for the storage node's data. Keep in mind that this is utilizing default configuration for logging and the set of JBoss ON agent plug-ins provided by Red Hat and does not include space requirements for third-party plug-ins or other components that are not part of the core installation.

I would also suggest going with at least 2 JBoss ON servers and storage nodes. This will provide a higher level of availability in cases of load spikes or if all 80 agents get restarted at the same time. If you can't do two JBoss ON servers, perhaps you can do at least two JBoss ON storage nodes so that measurement data read/writes do not overwhelm a single instance.

Oracle Database

This will really depend on what features of JBoss ON you are planning on using. You really need at least 10 GB of table space for the JBoss ON schema. However, this dramatically increases if you have a significant number of WAR files or other content managed resources being monitored or managed in your environment. A typical JBoss ON system could easily require 50 GB of table space and that amount can increase well above 100 GB if you are versioning content and utilizing provisioning bundles.

In most large environments, I see around 50 GB of table space being sufficient. However, in a few environments that have had several versions of each WAR deployed/redeployed and that utilized provisioning bundles to push out entire EAP installations to agents, I have seen tables space requirements near 150 GB.

To get a better idea of what your specific requirements might be, the suggestion is to setup an environment that contains an agent that represents your typical foot print. Then, review the table space required and multiply that by the number of agents.

I would also suggest that you ensure that your Oracle Database is setup in a way that allows you to add and expand table space in the future in cases where your system grows even larger.

80 JON agents (per each agent how much disk-space is required)

This will depend on the plug-ins used. However, typically 500 MB should be more then sufficient. However, if your agent will be managing a server that has tens-of-thousands of child resources, this may require additional space for the persisted inventory file. However, I rarely see inventory files that are larger then 100 MB and that will fit within the 500 MB with over 100 MB of free space to spare.

The JBoss ON server sizing recommendations knowledge solution may be helpful for you. It shows the scenario used for testing.

Hope that helps,

Larry O'Leary Red Hat Support Delivery https://access.redhat.com/support/contact/technicalSupport/

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.