whats the side effect in changing it to 10? or bigger?
btw, your answer does seem like the number of files are finally going down.
EDIT: Ok, i see that the values can only be from 1 to 8.. i'll set it to 8 and see if the number of files go down. Files are still coming in at a faster rate than the server's handling abilities.
Yup.. that does resolve the issue.
Since I have a seperate SQL server, changing the value of the DB Thread from 1 to 8 does not seem to impact the server availability and functionality. Right now i am down from 1700 to 700. So, Thank you Ty for your quick response in this matter.
This is how i would describe going above 4 threads.
Using 1 thread is like having the ability to bench 150 lbs. Weak for a large environment. Okay for a small set-up.
Setting it to 4 would be like being able to bench 300 lbs. Really good results.
Setting it to something like 8 would be like benching 307 lbs.
The moral of the story is; you reach a point of diminishing results once you get above 4.
Another issue on the same note... Inventory service keeps crashing now.. ??!@!!@???
DB Threads error is set to 10000... any ideas?
you should call support and verify thay you have the most recent Inventory Service running on your core server.
Anyone have experience with this setting in LANDesk 9.5 SP1? Still recommended and safe to bump threads up to 4?
We have about ~6000 nodes and I notice that .scns tend to pile up in ldscan folder and take a long time to process. For some reason, I dont remember them taking as long on LANDesk 9.0 to process.
We have plenty of 4 vCPUs / 8gb of RAM on Core Server and 4vCPUs and 16gb of SQL Server. 10GB link between both servers.
Here is how mine is set:
Core = 24 cores - 32GB memory
DB = 32 cores - 128GB memory
This processes the .scn files ~1-2 seconds on my server.
The inventory service will fail if the LDInv32.exe increases over 1,000,000K
Also, you may look at the tasks that are causing the scans to come in and see if there are some that are running that are not necessary.