How to Use the GSA SER Scheduler

Do you run many projects in GSA Search Engine Ranker? Then you have probably seen this message: “Out of Memory! Sorry, but you are using too many active projects or too many threads.” All your projects stop, and you have to start again.

The fix is already inside GSA SER. It is called the Scheduler, and most users never find it. In this guide, we show you where it is, what every setting does, and the settings we use on our own GSA SER servers.

Read the full blog post here : https://asiavirtualsolutions.com/how-to-use-gsa-ser-scheduler/

The Out of Memory one is almost always the thread count, not the project count — people run the default 300+ threads per project and the scheduler just delays when the crash happens. What actually fixed it for me was capping each project to ~50-80 threads and staggering the start times a few minutes apart, so they don't all fire their proxy and captcha burst on the same second. On a 16GB box that let me run more projects at once with fewer total threads and the crash basically went away. The scheduler is the band-aid, the thread cap is the fix.

harrysstone0

harrysstone0 said:

The Out of Memory one is almost always the thread count, not the project count — people run the default 300+ threads per project and the scheduler just delays when the crash happens. What actually fixed it for me was capping each project to ~50-80 threads and staggering the start times a few minutes apart, so they don't all fire their proxy and captcha burst on the same second. On a 16GB box that let me run more projects at once with fewer total threads and the crash basically went away. The scheduler is the band-aid, the thread cap is the fix.

Would you mind to share a screenshot of your scheduler, please?

harrysstone0 said:

The Out of Memory one is almost always the thread count, not the project count — people run the default 300+ threads per project and the scheduler just delays when the crash happens. What actually fixed it for me was capping each project to ~50-80 threads and staggering the start times a few minutes apart, so they don't all fire their proxy and captcha burst on the same second. On a 16GB box that let me run more projects at once with fewer total threads and the crash basically went away. The scheduler is the band-aid, the thread cap is the fix.

Here is a post I created in 2023 and again updated earlier this month, which specifically looks at the Out of Memory problem --- Thread control is just one of many ways to fix it  --- https://asiavirtualsolutions.com/how-to-avoid-the-out-of-memory-error-when-using-gsa-ser/