Users Guide

Optimizing Your System | Getting Started
OMNM 6.5.3 User Guide 113
For more about performance settings for monitors, see Understanding Performance Monitoring
on page 361.
For successful discovery of the resources on your network, OpenManage Network Manager requires
authenticated management access to devices. To get such access, you must provide the correct
SNMP community strings, WMI login credentials, and any other command-line (Telnet/SSH) or
browser (HTTP/HTTPS) related authentication, and SNMP must active on devices, if that is not
their default. Some devices require pre-configuration to recognize this management software.
Consult your network administrator or device manuals for instructions about how to enable them
and authorize OpenManage Network Manager as the management console.
CAUTION:
If you do not get access to the deepest level of authentications—for example the “enable” user’s—you
cannot access all of OpenManage Network Manager’s functionality.
MySQL Resizing, Starting and Stopping
MySQL Database Sizing— Installation includes the chance to select a size for your embedded
database. This should reflect expected use, and should be small enough that you leave enough
RAM for the application and operating system (at least 4G, typically).
NOTE:
The default MySQL login command line is: >mysql -u root --password=dorado
By default, installation optimizes the embedded database for the minimum hardware
requirement. This may not be sufficient for some environments when your database size
grows. You can set the database size during installation, and further tune performance
parameters in
..oware3rd\mysql\[version number]\my.cnf . Have your MySQL
operational expert review the links cited below to determine the best values for your
environment.
1.
innodb_buffer_pool_size=512m to 16382m
Best practice is to make your buffer pool roughly 10% larger than the total size of
Innodb TableSpaces. You can determine total tablespace size with the (free download)
MySQL Workbench application.
If your database size is 30G, ideally have a buffer size of 33G or more. You can also
investigate limiting database size or consider adding extra RAM. For dedicated
database server, we recommend 70%-80% of system server's RAM, for example use 16G
of RAM for a server with 24G RAM total.
To avoid operating system caching what is already cached by this buffer you may have
to make additional adjustments. This is not necessary on Windows, but for Linux you
need to set
innodb_flush_method=O_DIRECT.
You may want to make MySQL to use Large Pages for allocating Innodb Buffer Pool
and few other buffers. Tuning your VM to be less eager to swap things with
echo 0 >
/proc/sys/vm/swappiness
is another helpful change though it does not always
save you from swapping.
The optimal setting for Inno DB buffer is to have buffer pool hit rate of 1000/1000)
mysql> SHOW ENGINE INNODB STATUS\G
----------------------