...
Customising table views is described here: opCharts 3.2.2 - Customising Table Columns
Node info options
Customising node info options is described here: opCharts 3.2.2 - Customising Table Columns
Node list performance
As of See opCharts version 3.2.6 Node list performance has been improved significantly and will be noticeable on systems with higher node counts, particularly on the node list page and on and scheduled outage page.
There are two basic modes that can be run: db off and db on. db off has cache running in memory. db on uses the db for caching. When db is set to on, the nodesum files are cached into the db and filters are run against the db instead of doing the filters manually in memory. NMISx db caching is now the faster option. By default this config item is turned off, to enable this edit your opCommon.nmis file located at /usr/local/omk/conf/opCommon.nmis and set nmisx_db_cache_enable to 1. For systems with a low number of nodes, using the db may not show any performance improvement
| Code Block |
|---|
nmisx_db_cache_enable' => 1 |
There are two more configuration items that control how the cache works:
| Code Block |
|---|
nmisx_cache_min_age_before_refresh' => 60 |
This setting tells the app how long to wait before checking to see if the cache needs refreshing. In order to know if the cache needs refreshing we check the time the nodesum files are written and compare that against the time the cache was built. This is a simple optimisation. Since we access the cache quite often it gets a little expensive to check it several times a second, this prevents those checks for at least X seconds. The idea is that NMIS only writes the nodesum files at most once a minute so don’t bother looking more than that often.
| Code Block |
|---|
nmisx_cache_time' => 900 |
This setting controls how long the data will stay in the cache before it’s removed. This is only for db mode, in memory mode this will have no affect.