This section describes the minimum and recommended system requirements for a successful MySQL Enterprise Monitor installation.
This section describes the minimum hardware requirements for the Enterprise Service Monitor.
2 CPU Cores
2 GB RAM
Disk I/O subsystem applicable to a write-intensive database
This section describes the recommended hardware requirements for the Enterprise Service Manager.
4 CPU Cores or more
8 GB RAM or more
RAID10 or RAID 0+1 disk setup
The following table lists the minimum disk space required to install the Enterprise Service Manager and Monitoring Agent for each platform.
Table 3.1 Disk space Required
|Platform||Minimum Disk space Required by Service Manager||Minimum Disk space Required by Monitoring Agent|
|Linux x86 32-bit||N/A||600 MB|
|Linux x86 64-bit||1.3 GB||800 MB|
|Mac OS X||1.2 GB||700 MB|
|Solaris x86 32-bit||N/A||600 MB|
|Solaris x86 64-bit||1.8 GB||800 MB|
|Solaris Sparc 64-bit||1.7 GB||600 MB|
|Free BSD||N/A||300 MB (the FreeBSD installation does not include a JRE. It is assumed a compatible JRE is present on the system.)|
|Windows x86 32-bit||N/A||500 MB|
|Windows x86 64-bit||800 MB||500 MB|
The minimum disk space values for the Monitoring Agent include the disk space required by the backlog. The backlog is used if the agent loses contact with the Service Manager and cannot transmit the collected data. The collected data is stored on the agent's local file system until communication with the Service Manager resumes. Once normal communication is resumed, the entire backlog is transmitted, then deleted from the agent's local file system.
If you choose to install the bundled MySQL Server with the Enterprise Service Manager, you must also consider the amount of disk space required by the database. This value cannot be predicted as it depends on load, number of monitored instances, and so on.
If you are upgrading from a previous version of MySQL Enterprise Monitor, the upgrade process can create a full backup of all settings, including the local MySQL database used for the repository. This can result in a very large backup directory, several gigabytes in size, depending on the number of monitoring agents, and server load. Before upgrading, check the size of your existing installation and ensure you have enough disk space to run the upgrade. The upgrade also requires enough disk space for temporary files created by the upgrade process.