Nope you dont have 6k public proxies, maybe you have 6k dead public proxies or not working in SB. With such number of google passed proxies (6k) you would be able to harvest with XXk urls per second and you would pay at least high $xxx per month. To get good public proxies service (working 24/7) you would need good provider and at least ~$50 a month. If you are paying few bucks dont expect quality.
Also speed depends on footprints. Google is better and better in banning proxies. Dont use footprints with opertators, "powered by" unless there is no other way to harvest.
Well have you tried not using 5000 connections? Try 500 and see what happens, if you set the connections too high you just create so much overhead that you are going slower then if you didn't have that.
I don't actually use public proxies as a general rule, but here is a video where I show it.
https://www.youtube.com/watch?v=-0sggET1vWo
Bearing in mind that it is with just basic keywords. So try a test without footprints, just basic keywords, because thats the benchmark. As noted above, if you have obscure footprints, then 340 urls/s may actually be as fast as you are going to get.
I took your advices and got some proxies from proxygo. 3k google passed proxies(loving the speed, awesome service!) However the issue persists. I was getting around 2700 urls/s until 85%. It scraped around 450k urls until that point and it took 10 minutes. After that the threads started slowly declining and it's going slower and slower. The average urls/s is declining from 2500 urls/s to currently 350urls/s. The more it nears towards the end the slower it gets, the less and less threads it uses. I'm guessing it will take an hour to finish it up. Until the the average urls/s will get to 1.
from 0-85% - 10 minutes
from 85-100% - 3+ hours
So as you can see it's not the proxies. Any other opinion on this issue guys?
I've tried shorter runs, but it gets uglier. The slow declining happens again with every session. The more the sessions the more slower threads declining I will get. The longer the session, the longer I have to wait for the links to be exported. Either way it's no good.
Lower thread count will get me significantly lower speeds with these truly premium proxies, and the slow declining towards the end still happens.
Could this be a design flaw?
So even though I'm getting speeds of 2700 urls/s with these truly premium and expensive proxies, it seems like the average speed is less than 100u/s near the end, which means the full potential of these fast proxies won't ever be used.
I, like many, don't care about scraping all of the keywords, so how about an option in the automator to stop the harvesting process (and continue with the automator job) as soon as it detects lowering of the threads, can this be accomplished by any chance?
Almost all of the footprints from GSA contain something like: "powered by" "designed by" etc.. If I remove these I will be left with less than 10 footprints. I shall be getting footprint factory as well, but until then I need to scrape with the default footprints.
And a few questions if I may:
If I tick both: "Use server proxies" and "Load proxies from file" will it get proxies from both places, or just one?
If I also tick "Use Proxies" and "use server proxies and "load proxies from file" remain, will scrapebox use all of the sources and by what priority if yes?