Hi,

I am monitoring over 200 devices and my page takes about 5-15 secondes to load. Using Zenoss 3.2.1 and Chrome.

What type of devices are you monitoring ?

Are all those devices pulling information (routes) etc. Or only some of them ? I have checked I only have about 30 devices pulling information and the rest only sends a icmp packet to check if the device is still alive.

You must have good eyes. I had to zoom out to 50% (where I can't read anything) to get more than 50 devices shown. It is indeed taking a while to display. My suggestion is "don't do that" for what it's worth. By default maximized web page window, I see 25 devices... Even up to 40 shows fast. It may well be a bug, but the work-around is easy.

--

James Pulver

ZCA Member

LEPP Computer Group

Cornell University

tcaiazza:

You might want to increase your zope object cache and zope cache (both in zope.conf) as well as ensure that mysql caching and threads are appropriate. The infrastructure page taxes the global catalog (in zope) and calls methods which query for event totals in mysql. If the page has to wait for either (due to IO wait or invalidation) the page will load very slowly. Maximizing caching helps ensure that this condition only occurs during invalidation events, which can be handled by increasing the invalidation entry in the zeo.conf.

What are the current values? How large is your installation?

--Shane

tcaiazza:

Yeah that should definately be fine. I did try to replicate the problem, however, I couldn't duplciate the issue. My systems have massive amounts of resources, cache virtually everything and load balance across 40 zopes and is therefore not a good analog for this.

It might be interesting to login to mysql and show processes while refreshing the page. I'm interested in the queury time for the page.

--Shane

James:

Ouch! thats a serious spike.

Watching here we don't see more than a tiny ripple. Here's my test config:

[mysqld]

socket = /opt/zends/data/zends.sock

basedir = /opt/zends

datadir = /opt/zends/data

port = 13306

user = zenoss

innodb_file_per_table

skip_external_locking

key_buffer = 2048M                              # 25% of total memory on a machine that mainly runs MySQL is quite common

innodb_buffer_pool_size = 22528M                # The larger you set this value, the less disk I/O is needed to access data in tables

innodb_additional_mem_pool_size = 40M           # The more tables you have in your application, the more memory you need to allocate here

innodb_log_file_size = 512M                     # from 1MB to 1/N-th of the size of the buffer pool, where N is the number of log files in the group

innodb_log_buffer_size = 8M                     # allows large transactions to run without a need to write the log to disk before commit

innodb_flush_log_at_trx_commit = 2              # complicated, see the docs. 1 is safest

innodb_lock_wait_timeout = 50                   # timeout in seconds an InnoDB  transaction may wait for a row lock before giving up

max_allowed_packet = 64M                        # should be as big as the largest BLOB you want to use

table_cache = 24576                             # number of open tables for all threads

sort_buffer_size = 256M                         # Increase this value for faster ORDER BY or GROUP BY operations

read_buffer_size = 128M                         # If you do many sequential scans, you might want to increase this value

read_rnd_buffer_size = 16M                      # change the session variable only from within those clients that need to run large queries

myisam_sort_buffer_size = 1024M                 # size of the buffer that is allocated when sorting MyISAM indexes

thread_cache_size = 512                         # can be increased to improve performance if you have a lot of new connections

query_cache_size = 128M                         # amount of memory allocated for caching query results

query_cache_limit = 3072M                       # Don't cache results that are larger than this number of bytes, leave high for zenoss

thread_concurrency =24                          # Try number of CPU's*2 for thread_concurrency

innodb_flush_method=O_DIRECT                   # according to a DBA here are Rackspace, this setting is difficult to apply correctly

interactive_timeout = 600

wait_timeout = 86400

max_connections = 1500

max_user_connections = 1500

max_heap_table_size = 32768

[client]

socket = /opt/zends/data/zends.sock

user = zenoss

[mysql]

prompt = "zends> "

no-auto-rehash

[mysqldump]

quick

max_allowed_packet = 64M

[isamchk]

key_buffer = 1024M

sort_buffer_size = 256M

read_buffer = 256M

write_buffer = 256M

[myisamchk]

key_buffer = 1024M

sort_buffer_size = 256M

read_buffer = 256M

write_buffer = 256M