2024-07-17, 04:17 PM
(This post was last modified: 2024-07-17, 04:18 PM by TheDreadPirate. Edited 1 time in total.)
It shouldn't matter how frequent the scans are. As long as the scans aren't taking so long that they overlap. I'm pretty sure only one can happen at a time if that were to happen.
If scheduled scans are taking more than two hours, that is a problem.
This is such a hard problem to diagnose. Some people, like myself and a lot of the devs, have never seen this issue in our setups. And I don't set any thread limits for scans.
Some people, with similarly spec'd systems, can't seem to find away to stop it from happening.
If setting the thread limit to 1 doesn't work, we can try enabling debug logging to try to figure out what activity is tying up the database.
If scheduled scans are taking more than two hours, that is a problem.
This is such a hard problem to diagnose. Some people, like myself and a lot of the devs, have never seen this issue in our setups. And I don't set any thread limits for scans.
Some people, with similarly spec'd systems, can't seem to find away to stop it from happening.
If setting the thread limit to 1 doesn't work, we can try enabling debug logging to try to figure out what activity is tying up the database.