Increase threads versus adding MID servers

rgu
Tera Contributor

From the perspective of trying to speed up discovery scans, has anyone experimented with increasing the threads above the default of 25?

Currently our MID servers are set to 25 threads. When running discovery scans the servers are basically pegged. It is not clear to me what benefit there would be to increasing the threads.

From your experience, what are the bottlenecks on MID servers when running scans? CPU? Cores? RAM? Disk speed? Our MID servers are 2 CPU with 2 GB of RAM.

Besides adding additional MID servers, have you found other tweaks or strategies to speed up discovery scans?

(I did search the forum before posting this question. There were no recent discussions of this topic and/or details specific to Geneva.)

Thanks for your time.

9 REPLIES 9

Sharon Hobart
Mega Guru

The two changes I immediately make is to change the threads to between 75-100.   Also, go into the wrapper file on the mid server host and find the java memory line and change it from 512 to 1024 and make sure you remove the "#" sign to uncomment the line.   Bounce (restart) the mid server service after making these two changes.



My experience, especially with 64-bit, the two changes are a given to improve the efficiency of the mid server and speed up the processing.   I do not have any facts on speed up times but it does increase speed to a degree.         These tweaks do not necessarily eliminate the need of more mid servers but it can help reduce the time a scan can take.



Hope that was helpful or post if you need more information


Thank you for the reply. That is very useful information.


Let me know if you have additional questions.     If it was helpful - please mark as helpful.   Thanks!


I just looked at our MID servers, and "Maximum Java Heap Size" was already set to 1024 for all of them and the line was not commented out (assuming I looked at the right place). That must be the default for Geneva.



The location I looked was <path to MID server software>\conf\wrapper.conf. The specific line was "wrapper.java.maxmemory=1024".