Tags: hosting, tweeklyfm, twitter
So, Last.fm upgraded this weekend, which meant I had to reschedule Tweekly.fm. I decided on Monday 12pm GMT. The script started sending, only to cut out after 6minutes. A few minutes I get a message from my hosting company telling me I overloaded the server… Odd. It turns, I’ve been overloading the server every time, but because today’s Tweekly.fm run was in peak times, they had to stop the script.
So today, only 260 tweets were sent. Sorry about that! I’m going to optimise the script and send the rest of the tweets after-hours tonight. Your tweets are coming! Don’t worry!
It will be interesting to see how the optimisation will pan out, considering that I’m going to cut down on LOADS of SQL queries.
Sorry for the inconvenience! Tweekly.fm will resume it’s normal “time” this week. Saturday night GMT time.