Discovery rate tuning
The discovery rate attribute is the area with the most potential for tuning. The property with the most impact on performance is the number of discover worker threads. You can also use the in-progress sensors to monitor performance or improve it by specifying the session pool sizes.
If the server has sufficient spare capacity, you can increase this number and allow more sensors to run in parallel.
- A sensor in this stage is discovering a CI or CIs.
- A sensor in this stage finished discovering a CI or CIs, but is waiting for its results to be saved in the data store.
- A sensor in this stage saves its discovery results in the database.
By observing a discovery run and comparing the number of in-progress sensors that are in the started stage versus the number of in-progress sensors in the discovered or storing stages, you can assess whether attribute discovery is faster or slower than attribute storage for a particular environment. As with all changes to the collation.properties file, you must restart the server for the change to take effect.
In-progress sensors: STARTED, DISCOVERED, STORING.
If the number of (DISCOVERED + STORING) is smaller than STARTED, it might indicate that discovery is the performance bottleneck.
If the number of (DISCOVERED + STORING) exceeds STARTED, it might indicate that storage is the performance bottleneck.
Session and gateway pool sizes
2006-08-04 16:11:50,733 DiscoverManager [DiscoverWorker-34] WindowsComputerSystemAgent(192.168.16.181) INFO session.SessionClientPool - Session client [3x ssh2:/email@example.com]#9612508 waited 158.682 seconds for pool lock
In this case, the pool size for 10.10.250.1 is 20 but for all other hosts it is 3. You can look at the log messages like the one from the DiscoverManager logs and determine for which hosts the default session pool size is insufficient, and make the appropriate changes to the collation.properties file.
If your environment consists mainly of Windows computer systems, adjust this property upwards so it is equal to the number of discover worker threads.