- Jan 25, 2009
- 6,378
- 3,774
Thats just not how it works. It starts with 1 seed url and works thru it and then moves to the next. There are many reasons why this is best, which I won't go into.HI. Thanks for replying. Yes, I understand the concept of deep-crawling.
But the problem is that when I load lets say 50 URL as seed urls and set 2 levels deep, I would expect that 50 threads are created and deep crawling the 50 seed links separately.
But like I said, if I set level2 crawling on 50 URL it only uses 1 thread and crawls the URLs in cascade mode. It does not use several threads to crawl multiple seed urls at the same time. But If I use 1 level deep crawling the 50 URLs are crawled quickly by 50 threads at one time like they should.
So what seems to be the issue here?
Thank you for your response.
There is no issue. When your only looking at initial urls it can work with 50 threads, but as soon as you start crawling that uses a different segment of code and thus each url is worked 1 at a time in succession.
So in summary the expired finder is working as its supposed to. You can't change it, thats just how it is.
What you can do is run multiple instances of Scrapebox at once and thusly run multiple instance of the expired domain finder at once. There is no limit, you can run as many on the same machine as you want.