posted on May, 16 2010 @ 11:45 PM
Originally posted by JaxonRoberts
Mutter was unceremoniously taken offline
And it may not return soon, and when/if it does, it will likely be very different.
Soon after I took it offline, I posted here
that I was having a look and it
may not return.
As everyone knows, we've had some impressive increases in traffic. In fact, our overall traffic is very-nearly double what it was when mutter
launched one year ago. Since I designed it to utilize our thread/post system (in a more efficient way than actual threads) so that our staff could
easily moderate mutter, it ended up presenting some unexpected load on our servers as traffic increased.
Last week I was getting several daily alerts that the load on our web and database servers were increasing. Since I've recently suspected mutter may
be one of the culprits, I took it offline after I received three successive alerts on Friday... and immediate the load decreased to efficient levels.
As it turns out, there were about forty people simultaneously watching mutter... that's a lot for an AJAX application on an already busy server
And further testing this weekend confirms the issue. A simulated load of 30 mutterers (?) applied last night increased the load into alert levels...
remove the mutterers, load back to normal.
There's lots to do for the 2010 redesign, and some form (or forms) of instant communication is definitely in the mix. Improved chat. Member-to-member
instant messages. Video chat. Mutter-like in-page chat. All are being considered, and all are based on core technology that won't stress the server
cluster that delivers ATS pages.
I know, it sucks. But that, as they say, are the cold hard facts.