News for hackers. Stuff that matters.
Re:Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch... by w-ll on Friday March 08, 2013 @07:37PM (#5346718)
I dont know, but I would assume it has to deal with the fact you can't predict how long a job will take to complete, and a random selection would have more resources-more free-more often, verses FIFO where a group of really large tasks could halt everything.
Re:Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch... by manmal on Saturday March 09, 2013 @02:02AM (#5347678)
And what if they turned the whole thing into a request queue and workers get the "messages" as they become available? To ensure there are no timeouts, they could define a max time a request may stay in the queue, and then take it out and handle it with emergency workers or kill it?
Re:Coding Cloud Heroku May Face Lawsuit Over Bait-and-Switch... by kordless on Friday March 08, 2013 @08:49PM (#5346912)
That's exactly correct. Given jobs cleared out quick, that wouldn't necessarily be the case.