Comments on: Why is my tweekly.fm so late? http://shotbeak.com/2009/10/05/why-is-my-tweekly-fm-so-late/ Student, aspiring web entrepreneur and musician. Sat, 07 Jan 2012 10:25:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: shotbeak http://shotbeak.com/2009/10/05/why-is-my-tweekly-fm-so-late/comment-page-1/#comment-757 shotbeak Mon, 19 Oct 2009 12:29:36 +0000 http://shotbeak.com/?p=361#comment-757 Thanks for the comment. That is one of the ways I'm looking to solve it all. Blog post coming sometime this week detailing what I'm want to do, to fix Tweekly.fm. Thanks for the comment. That is one of the ways I'm looking to solve it all. Blog post coming sometime this week detailing what I'm want to do, to fix Tweekly.fm.

]]> By: xpaulbettsx http://shotbeak.com/2009/10/05/why-is-my-tweekly-fm-so-late/comment-page-1/#comment-756 xpaulbettsx Mon, 19 Oct 2009 05:54:37 +0000 http://shotbeak.com/?p=361#comment-756 Instead of batching all of the tweets up into one giant weekly cronjob, instead randomly pick a day of the week for each user (or better yet, a random time), and evenly bucket them - this way your server is running more often, but it won't have nearly as many users to deal with on each invocation. It'll also be way more predictable. <br><br>Another thing you could do is switch the service to using Amazon EC - this fits much better with your burst model, so that you can reserve 10-20 machines for the update, then drop them all later. Instead of batching all of the tweets up into one giant weekly cronjob, instead randomly pick a day of the week for each user (or better yet, a random time), and evenly bucket them – this way your server is running more often, but it won't have nearly as many users to deal with on each invocation. It'll also be way more predictable.

Another thing you could do is switch the service to using Amazon EC – this fits much better with your burst model, so that you can reserve 10-20 machines for the update, then drop them all later.

]]>