Author
Topic: Pandora Modules getting Grey easily (Read 1091 times)

Since Pandora 3.2.1 was launched we are using this Monitoring System, the problem is we have many modules created by plugin server and i think the server is getting heavy. Id like to know how can i optimize my Pandora Server (Data, Networ, Plugin and Prediction). I've heard someone saying that is possible to improve MySQL as well (there are two ways, one with one file to each table and another for write cache activated) but i dont know what a have to do.

The reason is, my agents are Greey very often (the Last contact is always red, the agents are often out of their pool time)

## The MySQL database server configuration file.## You can copy this to one of:# - "/etc/mysql/my.cnf" to set global options,# - "~/.my.cnf" to set user-specific options.## One can use all long options that the program supports.# Run program with --help to get a list of available options and with# --print-defaults to see which it would actually understand and use.## For explanations see# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients# It has been reported that passwords should be enclosed with ticks/quotes# escpecially if they contain "#" chars...# Remember to edit /etc/mysql/debian.cnf when changing the socket location.[client]port = 3306socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.[mysqld_safe]socket = /var/run/mysqld/mysqld.socknice = 0

[mysqld]## * Basic Settings#user = mysqlpid-file = /var/run/mysqld/mysqld.pidsocket = /var/run/mysqld/mysqld.sockport = 3306basedir = /usrdatadir = /database/mysqltmpdir = /tmplanguage = /usr/share/mysql/englishskip-external-locking## Instead of skip-networking the default is now to listen only on# localhost which is more compatible and is not less secure.#bind-address = 127.0.0.1## * Fine Tuning#key_buffer = 128Mmax_allowed_packet = 16Mthread_stack = 128Kthread_cache_size = 512# This replaces the startup script and checks MyISAM tables if needed# the first time they are touchedmyisam-recover = BACKUPmax_connections = 500table_cache = 2048thread_concurrency = 5## * Query Cache Configuration#query_cache_limit = 2Mquery_cache_size = 64M## * Logging and Replication## Both location gets rotated by the cronjob.# Be aware that this log type is a performance killer.#log = /var/log/mysql/mysql.log## Error logging goes to syslog. This is a Debian improvement :)## Here you can see queries with especially long duration#log_slow_queries = /var/log/mysql/mysql-slow.log#long_query_time = 2#log-queries-not-using-indexes## The following can be used as easy to replay backup logs or for replication.# note: if you are setting up a replication slave, see README.Debian about# other settings you may need to change.#server-id = 1#log_bin = /var/log/mysql/mysql-bin.logexpire_logs_days = 10max_binlog_size = 100M#binlog_do_db = include_database_name#binlog_ignore_db = include_database_name## * BerkeleyDB## Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.skip-bdb## * InnoDB## InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.# Read the manual for more InnoDB related options. There are many!# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.#skip-innodb## * Security Features## Read the manual, too, if you want chroot!# chroot = /var/lib/mysql/## For generating SSL certificates I recommend the OpenSSL GUI "tinyca".## ssl-ca=/etc/mysql/cacert.pem# ssl-cert=/etc/mysql/server-cert.pem# ssl-key=/etc/mysql/server-key.pem[mysqldump]quickquote-namesmax_allowed_packet = 16M

[mysql]#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]key_buffer = 32M

## * NDB Cluster## See /usr/share/doc/mysql-server-*/README.Debian for more information.## The following configuration is read by the NDB Data Nodes (ndbd processes)# not from the NDB Management Nodes (ndb_mgmd processes).## [MYSQL_CLUSTER]# ndb-connectstring=127.0.0.1

## * IMPORTANT: Additional settings that can override those from this file!# The files must end with '.cnf', otherwise they'll be ignored.#!includedir /etc/mysql/conf.d/

If the problem is the performance of the database, one alternative is to use mysql with innodb. In my case, I use one file per table (it's working fine to me). Remember: If you are going to change the Storage Engine of your MySQL from MyISAM to InnoDB make a FULL BACUKP before ;-) It's better to be safe than sorry.

The database server is a quad-core Xeon 3.2GHz with 4GB of RAM:

The specific confs that I use in my.cnf to do the job are:

------------------------------------------------------------# You can set .._buffer_pool_size up to 50 - 80 %# of RAM but beware of setting memory usage too highinnodb_buffer_pool_size=2G

I'm not a mysql guru... I start to use this settings some years ago when I had the first problems with performance of the MySql database.. I did some research and test that time, and those settings worked fine to me.

I advice you to take a look at:http://openideas.info/wiki/index.php?title=Pandora_3.0:Documentation_en:Anexo_AjusteMySQL

I'm not a mysql guru... I start to use this settings some years ago when I had the first problems with performance of the MySql database.. I did some research and test that time, and those settings worked fine to me.

I advice you to take a look at:http://openideas.info/wiki/index.php?title=Pandora_3.0:Documentation_en:Anexo_AjusteMySQL

I hope this helps.

Regards.

Bloody hell ive never seen this doc before, looks good, ill take a look! thanks!