Frozen threads?
Hi,
Recently I've been unable to run gsa ser at speeds which I'd like. Ser seems to run just fine and very fast at first when I start all the projects, but after some time (30 minutes - 1-2 hours) it is only using a very small amount of threads. I've set it to 2k threads at the moment, but only 1-2/8 projects (I only see these in the log for several minutes) will use threads and only 300-400 at most. However when I stop all the projects with the big red stop button, the projects which were running just fine will quickly finish what they were doing and stop, as expected. But the last 6-7/8 projects will not finish. I have sometimes seen that the projects which were halted will finish as expected, yet it's first after 5-20 minutes if they ever finish. Also before these halted projects will finish as expected, ser says it's only using something like 5-20 threads, yet the stopping project will post a LOT into the log.
I've also seen this behavior happen and resolve itself after a few hours. Some projects will not submit, search, or anything for a long time then suddenly start going crazy. I'd like to note that all my projects have lists of 3 million urls imported, 168 search engines enabled, 100k keyword lists, and lots of public proxies along with some private ones though it usually is plenty for me with just public proxies.
The screenshot below shows how 2/8 projects have stopped after pressing the stop button, yet 6 projects are still hanging around only using 6 threads. The screenshot is taken 7 minutes after stopping all the projects, yet they're not stopping and still aren't 35 minutes later. They're behaving the same way while running as they're not doing anything.
Please tell me if I can provide more information if my problem is unclear @Sven and I'm sorry for the wall of text, but I wanted to make my problem as clear as possible. I'm also not sure if this is intended, but it just seems very weird that projects will not do a single thing for a looong time, also even after all projects have been stopped and it's really killing my LpM.
Comments
I'm a bit surprised as that was obviously a server class cpu that would be used for sites that get hundreds of thousands of visits a day so assumed it would take a lot more of a beating, but there is obviously a software bottleneck somewhere.
In fact right now it is using 8 threads
I am running a complete churn and burn so its every kind of link checked so it isnt stopping because of filters. Still should be using all 200 threads.