Scrapebox links checker - Whats UP?

M1ndfluX

Banned - Selling via PM
Joined
Dec 23, 2009
Messages
1,129
Reaction score
882
Hey guys,


Any more of you experiencing slow link checking with SB?

I know when i first got the tool a year ago the first versions checked links with almost the same speed as the poster.
But it seems the last couple of months things get slower and slower.

I have xsservers biggest vps's and when i run it at 40 threads/maximum timeout.
Every few secs it 'freezes' for a few secs and as i recall it correctly, the earlier versions didnt stop every few secs before continuing...

When i do 75 threads for instance things get unstable and it crashes.


Any thoughts on this one?
 
I do notice a little slow down since previous versions, but nothing major. I simply set the link checker up, minimize the vps window, and come back 30 minutes to an hour later to check results on a big list. Even on 40 threads it is still pretty fast for me.
 
I do notice a little slow down since previous versions, but nothing major. I simply set the link checker up, minimize the vps window, and come back 30 minutes to an hour later to check results on a big list. Even on 40 threads it is still pretty fast for me.

Hi Kickflip, thanks for the reply, appreciated.

So no stuttering when you check? Mine stops every few seconds for a few seconds.

How many threads do you usually check with?

TY
 
i'm using it on my laptop and VPS and i have also noticed a huge slowdown. Not sure what it is.
 
same problem to me, a list of 15k in about 2h, very slow
tried to tweak with connections but no succes in making it faster
 
So no stuttering when you check? Mine stops every few seconds for a few seconds.

How many threads do you usually check with?

The freezing and stopping is usually because of the timeout counter running down while it finishes other threads running. I do notice it too, but that is why I just minimize it and check it later.

I run 45 or 50 threads always. It takes 30 minutes for me to check 9,000 sites approximately. If you are doing BIG lists I would only suggest to run link checker when you go to sleep each night, or when you are leaving the house for few hours etc.
 
Ok guys, I just did a side by side test and here are some interesting results.

Setup #1:
45 Threads
25 Public Proxies
3 websites
11,754 blogs (mostly NOT FOUND, moderated blogs)
= 45 minutes , and 600 MB bandwidth used.

Setup #2:
50 Threads
131 Public Proxies
41 websites
11,761 blogs (mostly AUTO APPROVE blogs)
= 21 minutes, 3500 MB bandwidth used.

So clearly the results can be a CRAZY difference. Now, I have a feeling one of the big differences is types of proxies being used. I believe the optimal setting is 40-50 threads MAX.
 
The freezing and stopping is usually because of the timeout counter running down while it finishes other threads running. I do notice it too, but that is why I just minimize it and check it later.

I run 45 or 50 threads always. It takes 30 minutes for me to check 9,000 sites approximately. If you are doing BIG lists I would only suggest to run link checker when you go to sleep each night, or when you are leaving the house for few hours etc.

Hi Kickflip,


Yeah thats what i thought.

Basically i close my vps servers and dont bother, but as you know time is money ;)

Noticed your test.

I check my links without proxies.
All are now posting so i cant do a test atm but tomorrow ill check too.
 
I know when i first got the tool a year ago the first versions checked links with almost the same speed as the poster.
But it seems the last couple of months things get slower and slower.

I just split test v1.12.3 from a year ago against v1.15.8 and found the exact opposite.

Using 40 connections with a 40 second timeout took the old version 8 minutes 44 seconds.
http://i51.tinypic.com/b9elic.png

Same 40 connections and the same 40 second timeout took the latest 7 minutes 37 seconds.
http://i56.tinypic.com/ajxon7.png

This was using the same list, flushing the DNS resolver cache in between tests etc the latest was slightly faster. This makes sense because the latest uses a higher performance grid which takes less time to populate/update the cells with data and nothing at all has changed to effect the connections.
 
I just split test v1.12.3 from a year ago against v1.15.8 and found the exact opposite.

Using 40 connections with a 40 second timeout took the old version 8 minutes 44 seconds.
http://i51.tinypic.com/b9elic.png

Same 40 connections and the same 40 second timeout took the latest 7 minutes 37 seconds.
http://i56.tinypic.com/ajxon7.png

This was using the same list, flushing the DNS resolver cache in between tests etc the latest was slightly faster. This makes sense because the latest uses a higher performance grid which takes less time to populate/update the cells with data and nothing at all has changed to effect the connections.
Today I try to check 5K links 3 times and every time buildin link checker hangs up so I roll back to 1.15.6 version and all becomes fine.
Another problem 500K link trimmed to root than I try to remove duplicate domains scrapebox hangs up but 1.15.6 can do this job just fine.
 
Today I try to check 5K links 3 times and every time buildin link checker hangs up so I roll back to 1.15.6 version and all becomes fine.
Another problem 500K link trimmed to root than I try to remove duplicate domains scrapebox hangs up but 1.15.6 can do this job just fine.

Hi BSON,


Same here the latest update hanged up every time on my vps. Switched back also. Shame cause i was waiting for the keyword url remover in the harvester for a very long time...
 
I just split test v1.12.3 from a year ago against v1.15.8 and found the exact opposite.

Using 40 connections with a 40 second timeout took the old version 8 minutes 44 seconds.
http://i51.tinypic.com/b9elic.png

Same 40 connections and the same 40 second timeout took the latest 7 minutes 37 seconds.
http://i56.tinypic.com/ajxon7.png

This was using the same list, flushing the DNS resolver cache in between tests etc the latest was slightly faster. This makes sense because the latest uses a higher performance grid which takes less time to populate/update the cells with data and nothing at all has changed to effect the connections.

Hi SF,


Thanks for the reply, appreciated.

Difference in speed now and then can happen because of a lot of issues, like blog size, amount of comments etc etc... Something i am not going to say to you as you already know that.

Fact is. Back then the link checker just went on and on without a hitch.

The latest versions for me stops for a few secs, go for a few secs etc... Sorry, english isnt my native language ;)
 
Freezing up here too. Ever since I upgraded to 1.15.7. How do I get a copy of 1.15.6? I *really* need it.
 
I also got problems with SB link checker. For you guys, its slow. But for me, it simply doesn't work :(

Every time I want to check links, 404 errors begin to pop... NO matter how big or small is the size of blogs list. I've tweaked max conn/timeout settings but the problem still exists.

Bk...
 
I use 25 connections for link checker with 10 private proxies. Just import 2k backlinks to check, it always down ! WTF !

Lol.. Again crashed with 1k links.. haha it's soo funny..
 
Last edited:
Yep, same issue here, actually wanted to post this myself a few days ago
 
15.7 never worked for me at all. Massive problems. All my copies are back to the 15.6 version

Besides that i also have issues with my own auto approved lists. Worked like a charm but since a few weeks the succes rates drop also.

Running 4 copies on 4 vps servers with over 100 private proxies so i guess thats not the problem.

I am sure SF will come up with a better update soon ;)
 
I use 25 connections for link checker with 10 private proxies. Just import 2k backlinks to check, it always down ! WTF !

Lol.. Again crashed with 1k links.. haha it's soo funny..

Use the rollback function to get the 15.6 version back. solved my crashing problems.
 
Use the rollback function to get the 15.6 version back. solved my crashing problems.

I did.. I never use that problem before the new version, after read your post about roll back, i did but it did not solve my crashing problems..
 
Back
Top