Comments on: Rate Limiting Your Workers to Play Nicer with Other API’s https://blog.iron.io/rate-limiting-your-workers-to-play/ Scalable serverless application tools to run background tasks with Docker containers and manage messaging queues with cloud elasticity and handheld customer support. Mon, 14 Jun 2021 07:55:40 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Travis Reeder https://blog.iron.io/rate-limiting-your-workers-to-play/#comment-45 Sat, 18 Feb 2012 21:43:36 +0000 http://ironio2.wpengine.com/?p=220#comment-45 Hi Jared,

No it doesn’t count towards machine time. The delay time is free.

]]> By: Jared https://blog.iron.io/rate-limiting-your-workers-to-play/#comment-44 Sat, 18 Feb 2012 14:18:08 +0000 http://ironio2.wpengine.com/?p=220#comment-44 Question on pricing… Does the delayed time count as machine time?

]]> By: Travis Reeder https://blog.iron.io/rate-limiting-your-workers-to-play/#comment-43 Fri, 10 Feb 2012 22:23:05 +0000 http://ironio2.wpengine.com/?p=220#comment-43 Hi Luke,

We recommend to use the ‘delay’ parameter on queue rather than using the scheduler to do these kinds of things because there is a limit on the number of schedules you can have and it’s a lot more efficient for us on the backend.

]]> By: Luke https://blog.iron.io/rate-limiting-your-workers-to-play/#comment-42 Fri, 10 Feb 2012 21:52:43 +0000 http://ironio2.wpengine.com/?p=220#comment-42 This also works really well when scheduling tasks:
start_at = Time.now
10000.times do |i|
worker = MyWorker.new
worker.schedule start_at: start_at
start_at += 30
end

]]>