Home/ Questions/Q 3722986
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T06:06:21+00:00

Currently, my Nokogiri script iterates through Google’s SERPs until it finds the position of

  • 0

Currently, my Nokogiri script iterates through Google’s SERPs until it finds the position of the target website. It does this for each keyword for each website that each user specifies (users are capped on amount of websites & keywords they can track).

Right now, it’s run in a rake that’s hard-scheduled every day and batches all scrapes at once by looping through all the websites in the database. But I’m concerned about scalability and swarming Google with a batch of requests.

I’d like a solution that scales and can run these scrapes over the course of the day. I’m not sure what kind of solution is available or what I’m really looking for.

Note: The amount of websites/keywords change from day to day as users add and delete their websites and keywords. I don’t mean to make this question too superfluous, but is this the kind of thing Beanstalkd/Stalker (job queuing) can be used for?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You will have to balance two issues: Scalability for lots of users versus Google shutting you down for scaping in violation of their terms of use.

    So your system will need to be able to distribute tasks to various different IPs to conceal your bulk scraping which suggests at least two levels of queuing. One to manage all the jobs and send them to each separate IP for subsequent searching and collecting results and queues on each separate machine to hold the requested searches until they are executed and the results returned.

    I have no idea what Google’s thresholds are (I am sure they don’t advertise it) but exceeding them and getting cut off would obviously be devastating for what you are trying to do so your simple looping rake task is exactly what you shouldn’t do after a certain number of users.

    So yes, use a queue of some sort but realize that you probably have a different goal from the typical goal of a queue in that you want to deliberately delay jobs rather that offload word to avoid UI delays. So you will be seeking ways to slow down the queue rather than have it just execute job after job as they arrive in the queue.

    So based on a cursory inspection of DelayedJob and BackgroundJobs it looks like DelayedJob has what you would need with the run_at attribute. But I am only speculating here and I am sure an expert would have more to say.

    • 0