Mon, Aug 10, 2009 12:12 AM
Fri, May 22, 2009 11:34 AM
Thu, May 7, 2009 11:57 AM
Wed, Apr 8, 2009 08:00 AM
Sun, Feb 22, 2009 06:00 PM
Mon, Jan 5, 2009 12:08 AM
Wed, Dec 17, 2008 01:26 AM
Lots of people talk about scaling and performance. But, are they preparing for all the things that could happen? There are multiple problems and there is not one solution to solve them all.
Everything is running fine and BAM! – your site is linked from the front page of Yahoo! What do you do? How can you handle that sudden rush of traffic. Requests per second are running 5x normal levels. Servers have CPU spikes. Daemons are hitting the maximums. You are running out of bandwidth. How could you have been prepared for this? What are the tools and techniques for this type of sudden rush?
Or, lets say you have just come out of a meeting where everyone discovered that your site is growing in traffic 70% – 80% year over year. That means that 1 million page views this month will be nearly 3 million this time in 2 years. How can you plan for that? You don’t want to redesign the whole architecture every 2 years. What methods could be used to deal with this constant long term growth?
While there is no magic bullet for either of these scenarios, there are techniques used by many sites out there to help you get through these situations. This session will cover some of these techniques and talk about their pros and cons.
I must admit, this if the first time since 2000 that I am a little intimidated to speak at a conference. The people that present and attend Velocity are so awesome. I just hope I don't disappoint.
I am happy to announce Wordcraft 0.7. There are two big changes in this release. On the front end, I added a simple search. It just uses a LIKE clause. But, I figure a lot of blogs never reach 1,000 posts. Even at 10,000 posts, a LIKE would not be too bad. On the backend, I have switched the post editor to TinyMCE. YUI's editor is decent, but it needs polish. Perhaps my time with Wordpress just made me more familiar with it. TinyMCE does save XHTML. I put some code in the PHP side to use Tidy if it is available to convert it to HTML 4.01, which I prefer.
Also in this release: