News for hackers. Stuff that matters.
Re:Scalable Image Processing Using Hosted Cloud Services by jblake on Tuesday May 29, 2012 @11:35PM (#4041239)
What would be the advantage of using this vs using Resque + S3 + heroku worker auto-scaling?
Re:Scalable Image Processing Using Hosted Cloud Services by treeder on Wednesday May 30, 2012 @02:33PM (#4044121)
No resque setup/management, no auto-scaling setup, scale huge with zero effort (go from processing one image to millions without lifting a finger), redundancy and reliability (how are you going to ensure that with your Resque?), full visibility into your tasks, etc.
Re:Scalable Image Processing Using Hosted Cloud Services by scosman on Tuesday May 29, 2012 @11:47PM (#4041277)
I've set up this exact flow using delayed_job, heroku, S3 and paperclip (an awesome gem wrapping imagemagick). I'm with jblake, I don't see the advantage.
Re:Scalable Image Processing Using Hosted Cloud Services by nico_h on Tuesday May 29, 2012 @11:50PM (#4041281)
Presumably: cheaper, easier set up. Sounds a lot like PiCloud.com
Re:Scalable Image Processing Using Hosted Cloud Services by jblake on Wednesday May 30, 2012 @12:00AM (#4041312)
The way I understand their pricing (.05/hr, .10/hr, .15/hr based on minutes jobs get pulled off queue), I'm essentially paying 3x more for priority queuing that I can bypass by setting the INTERVAL=3 in Resque. Hm. This an expensive way to set a variable.
Re:Scalable Image Processing Using Hosted Cloud Services by treeder on Wednesday May 30, 2012 @02:36PM (#4044137)
IronWorker is billed by the second so if an image takes 5 seconds to process, you only get billed for 5 seconds of the hour. No need to deal with auto-scaling heroku workers to keep your costs down.

And priority on IronWorker has a much different meaning than setting it on your own private Resque instance so comparing that based on price isn't really a fair comparison.