OK. I see that if I slow down, I won't overflow my allotted CaptchaTronix buffer.
So...that saves me money on solves.
There seem to be specific advantages to running slowly or lightning-fast.
I guess if you're at a point where all your projects and sub-projects' link demands (HUUUUNGRY!!! lol) means you have to get those super-high VPM numbers, I get it. It's essential you not waste a minute in that 24 hour period, or any processing resources.
But I'm not at that point, just yet. Probably, not for a bit.
So, leaving GSA on with way fewer threads, also spreads out the links, time-wise. For sites crawled by a/the particular SE ur trying to help recognize the worth of your brand, it then (potentially) sees these new links throughout the day.
Just a thought. For now I think slowing down makes sense in my case. Until it doesn't any longer? lol I think that's the goal of a place you want to reach.
Therefore, I'm also checking out the Scheduler, which I've never used. (I mostly rely on Select by Mask, done manually)
I guess at some point the answer is to order a higher-thread package, and slowly work up to prevent overflow, and only so much added headroom that you're very nearly up to it only at peak operations, maybe with ~15%(?) to spare? Keep repeating this process until your needs outgrow each higher-rung package of threads? Kind of like re-potting a houseplant in progressively larger pots as it grows.