How Many Threads To Use For Website Contact and SER

What are the general rules of thumb for how many threads we should use in GSA Website Contact and Search Engine Ranker?
Primarily, I will be scraping, checking, and submitting forms with GSA Website Contact. I’ll be using SER later this year. 
I have several different types of projects and I will be using different amounts of proxies at different times. All private HTTP proxies in the US and Canada. In some months/projects I will be using 10 proxies and in other months/projects I will be using 50 proxies.
I currently use 10 threads with 60 proxies. At the bottom of Website Contact, the CPU seems to go between 3 and 15%. Memory goes up to 200mb so far. 4 current projects
1- 1000 sites (only using verified list uploads, no scraping, just checking and sending)
2- 29k sites (only using verified list uploads, no scraping, just checking and sending)
3- 30k sites (only using verified list uploads, no scraping, just checking and sending)
4- 98k sites (Does scraping, checking, sending)
How many threads should I be using? while using the same 10 proxies, and while using the same 50 proxies, across all projects

Minimum threads threshold

Hi @Sven
Is there any possibility to add Min. threads threshold in Global settings?
For example, I want to set my threads to 600 and decrease threads when memory usage is above 2900 MB. In this situation, SER may decrease threads to even 100 while It can handle even 400 threads at that moment. So if there is Min. threads threshold, I can set it to 400 and when SER memory usage is above 2900 MB, It can change my threads between 400 and 600 to manage its high memory usage but not less.

Too many MaintenanceTimer and CleanCursors Threads

I am using jconsole to check for the number of threads and i see a lot of MaintenanceTimer threads and CleanCursor Threads.

  1. What are these threads ?
  2. Is it related to any mongodb configurable options ?

Any pointers on these will be helpful.

There are about 300+ threads of which i see 180+ threads related to MaintenanceTimer and CleanCursors

Name: CleanCursors-180-thread-1 State: TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ ConditionObject@5b478a71 Total blocked: 0 Total waited: 364

Stack trace: sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.parkNanos( java.util.concurrent.locks.AbstractQueuedSynchronizer$ ConditionObject.awaitNanos( java.util.concurrent.ScheduledThreadPoolExecutor$ DelayedWorkQueue.take( java.util.concurrent.ScheduledThreadPoolExecutor$ DelayedWorkQueue.take( java.util.concurrent.ThreadPoolExecutor.getTask( java.util.concurrent.ThreadPoolExecutor.runWorker( java.util.concurrent.ThreadPoolExecutor$

The number of threads keeps decreasing. Help me.

My vps are fine. cpu usage is within 10% and ram usage is 200mb.

I bought this from Solidseo
I bought 50 Private proxy products from Solidseo and I am using them.

At first, when threads set 100, it goes back and forth between 90 and 100.
But after 9 hours, he goes back and forth between 30 and 40.

I’m using a catchall emil and I’m using three.

Also, I am using the list of serverified lists. I do not use scape

Newbie questions – only 17 threads running of 200 available


I’m testing my first GSA SER project, everything seems to works fine except one major problem.
I set up max 200 theads, but GSA runs much more less (for example 10-50 threads at a time with ~50-75 LPM). Sometimes up to 100+ threads with 130+ LPM. All system resources almost free – pls find attached screenshot. I use a premium links list. Speedtest shows about 100-150 Mbs speed. Xevil runs at another machine and have a lot of free resources.
Why cant GSA run maximum amount of threads?

Hope Sven or smb else could help me with it.
Best regards.

Cores, threads and sockets: what does it mean the calculation $T = tcs$ and the number on windows task manager performance?

Well, suppose then we have an CPU system such as:

Thread(s) per core $ \equiv t$ : 4

Core(s) per socket $ \equiv c$ : 4

Socket(s) $ \equiv s$ : 1

Then, we must to perform a simple calculation such as: $ 4 \cdot 4 \cdot 1 = 16 $

Therefore, in general we have:

$ $ T = t\cdot c \cdot s \tag{1}$ $

I guess that the equation $ (1)$ gives you then the total number of threads which your system can handle simultaneously.

On the other hand, consider the figure, of windows task manager, in the following:

enter image description here

In the red box we clearly see the number of "Threads". So I would like to know:

What is the difference between the number given by formula $ (1)$ and the number given by windows task manager?

200 Lifetime Threads ONE-TIME Payment for 99.95 USD Only

200 Lifetime Threads ONE-TIME Payment to Solve UNLIMITEDLY!

CAPTCHAs.IO has decided to give its users and every developer an offer that would help them greatly with their CAPTCHA automation projects and applications for a lesser cost.

End-users and developers can now enjoy UNLIMITED solves with 200 threads for just the cost of a ONE-TIME payment of $ 99.95 USD fixed price.

To order please email


what determines the amount of threads you can use

what determines the amount of threads you can use ? (in order to get more done in the same amount of time)

the reason im asking is because i have seen some posts say they would need minimum 16GB of ram,
but also that GSA SER is 32 bit & that anything over 3GB of ram would not make any difference.

ive taken account of various things to try & make it more efficient etc. & keeping an eye of
memory & cpu usage at bottom of GSA SER interface.

i have 4gb of ram, so would getting more ram make any difference ?

1000 Threads w/ Unlimited Daily Solves for Just $250 a Month!

I’d like to offer you another round of special offer. We have now the MEGA #2 special package. This package is highly different from those that are offered currently in our site.
This package is a big budget saver. You can enjoy <b>1000 threads for just $ 250 USD a month</b> and it comes with <b>UNLIMITED daily solves</b> too…
1. 1000 Threads
2. UNLIMITED Daily Solves
3. 20 Elite Proxies
To subscribe just go to
Thank you and God bless!