Not in the clamor of the crowded street, not in the shouts and plaudits of the throng, but in ourselves, are triumph and defeat.--Henry Wadsworth Longfellow
REDIRECT ALERT!(Scroll down past this mess if you're trying to read an archived post. Thanks. No, really, thanks.)
Due to my inability to control my temper and complacently accept continued silliness with not-quite-as-reliable-as-it-ought-to-be Blogger/Blogspot, your beloved Possumblog will now waddle across the Information Dirt Road and park its prehensile tail at http://possumblog.mu.nu.
This site will remain in place as a backup in case Munuvia gets hit by a bus or something, but I don't think they have as much trouble with this as some places do. ::cough::blogspot::cough::
So click here and adjust your links. I apologize for the inconvenience, but it's one of those things.
Over the weekend, we've made some additional changes which have helped performance. We've addded more machines to the cage and rewritten some portions of the code which were overutilizing system resources.
There's still more to do and we'll be making more changes this week (hardware and software) to further improve Blogger's responsiveness.
Posted by Jason at 23:52
Friday, March 18, 2005
Yesterday, we increased the server capacity of blogger.com by 20% in order to address some of the stability problems we are seeing. This has had a positive impact but there is more to do.
What we are seeing is that individual application servers will trend toward 100% CPU usage over time - simply, the appservers get pegged and users on those servers encounter paralyzingly slow load times throughout the site. Over the course of the next week, we will be doubling the number of machines responsible for serving blogger.com in order to address this.
Users with more than 500 posts are also being severely hampered at this time. We believe this is due to an improper use of system resources when users of such blogs either access the Edit Posts page or attempt to publish. We will be testing a potential fix to this problem over the next couple days and hope to push it to production early next week. Because of the extent of the change, we need to fully assess the impact on the service before deployment.
This blog will be updated with additional news on these solutions to the current problems.
Posted by Jason at 11:41
I wonder what all that means? posted by Terry at