It’s critical to your business. It affects revenue. It’s how people who can’t come to you perceive you.

It’s your Web site.

Its complex. Abstract. Lots of conflicting ideas and forces are involved. Everyone says they now the best thing for it. Finger-pointing. Door slamming. Screaming.

Am I describing your Web site and the team that supports it? Or your teenager?

If you think of your Web site as a teenager, you begin to realize the problems that your facing. Like a teenager, it has grown physically and mentally, and, as a result, thinks its an experienced adult, ready to take on the world. However, let’s think of your site as a teenager, and think back to how we, as teenagers (yeah, I’m old), saw the world.

MOM! This doesn’t fit anymore!

Your Web site has grown as all of your marketing and customer service programs bear fruit. Traffic is increasing. Revenue is up. Everyone is smiling.

Then you wake up and realize that your Web site is too small for your business. This could mean that the infrastructure is overloaded, the network is tapped out, your connectivity is maxed, and your sysadmins, designers, and network teams are spending most of your day just firefighting.

Now, how can you grow a successful business, or be the hip kid in school, when your clothes don’t fit anymore?

But, you can’t buy an entire wardrobe every six months, so plan, consider your goals and destinations, and shop smart.

DAD! Everyone has one! I need to have one to be cool!

Shiny.

It’s a word that has been around for a long time, and was revived (with new meaning) by Firefly. It means reflective, bright, and new. It’s what attracts people to gold, mirrors, and highly polished vintage cars. In the context of Web sites, it’s the eye-candy that you encounter in your browsing, and go “Our site needs that”.

Now step back and ask yourself what purpose this new eye-candy will serve.

And this is where Web designers and marketing people laugh, because it’s all about being new and improved.

But can you be new and improved, when your site is old and broken?

Get your Web performance in order with what you, then add the stuff that makes your site pop.

But those aren’t the cool kids. I don’t hang with them.

Everyone is attracted to the gleam of the cool new Web sites out there that offer to do the same old thing as your site. The promise of new approaches to old problems, lower cost, and greater efficiencies in our daily lives are what prompt many of us to switch.

As a parent, we may scoff, realizing that maybe the cool kids never amounted to much outside of High School. But, sometimes you have to step back and wonder what makes a cool kid cool.

You have to step back and say, why are they attracting so much attention and we’re seen as the old-guard? What can we learn from the cool kids? Is your way the very best way? And says who?

And once you ask these questions, maybe you agree that some of what the cool kids do is, in fact, cool.

Can I borrow the car?

Trust is a powerful thing to someone, or to a group. Your instinctive response depends on who you are, and what your experiences with others have been like in the past.

Trust is something often found lacking when it comes to a Web site. Not between your organization and your customers, but between the various factions within your organization who are trying to interfere or create or revamp or manage the site.

Not everyone has the same goals. But sometimes asking a few questions of other people and listening to their reasons for doing something will lead to a discussion that will improve the Web site in a way that improves the business in the long run.

Sometimes asking why a teenager wants to borrow the car will help you see things from their perspective for a little while. You may not agree, but at least now it’s not a yes/no answer.

YOU: How was school today? – THEM: Ok.

Within growing organizations, open and clear communication tends to gradually shrivel and degenerate. Communications become more formal, with what is not said being as important as what is. Trying to find out what another department is doing becomes a lot like determining the state of the Soviet Union’s leadership based on who attends parades in Red Square.

Abstract communication is one of the things that separates humans from a large portion of the rest of the animal kingdom. There is nothing more abstract than a Web site, where physical devices and programming code produce an output that can only be seen and heard.

The need for communication is critical in order to understand what is happening in another department. And sometimes that means pushing harder, making the other person or team answer hard questions that they think you’re not interested in, or that you is non of your business.

If you are in the same company, it’s everyone’s business. So push for an answer, because working to create an abstract deliverable that determines the success or failure of the entire firm can’t be based on a grunt and a nod.

Summary

There are no easy answers to Web performance. But if you consider your Web site and your teams as a teenager, you will be able to see that the problems that we all deal with in our daily interactions with teens crop up over an over when dealing with Web design, content, infrastructure, networks and performance.

Managing all the components of a Web site and getting best performance out of it often requires you to have the patience of Job. But it is also good to carry a small pinch of faith in these same teams, faith  that everyone, whether they say it or not, wants to have the best Web site possible.

If you use GrabPERF on a regular basis, the somewhat flaky navigation method has become second nature to you. In fact, to circumvent some of the idiosyncrasies, you have probably bookmarked your favourite pages.

Yesterday, I broke your links.

When I redesigned GrabPERF in February 2006, I had just discover the require function in PHP, and decided to build the entire the structure using a single container page as the framework, and individual functions called using URL parameters.

As time went on, my own “brilliance” started to get in the way of maintaining and updating the code. It took me 10-15 minutes to figure out how I constructed pages, and then find the right code to fix or update.

Yesterday, I got completely fed up with this structure.

Now, all functions have their own unique pages, making maintenance a snap. And as an added benefit, I can now effectively track the usage of individual pages, so I know where to through development efforts.

Some of the changes.

http://grabperf.org/homepage.php?page=compare&test=2&tests%5B%5D=276&tests%5B%5D=277&tests%5B%5D=279&tests%5B%5D=280

becomes

http://grabperf.org/compare.php?test=2&tests%5B%5D=276&tests%5B%5D=277&tests%5B%5D=279&tests%5B%5D=280

http://grabperf.org/homepage.php?page=scatter&test=277&hours=2

becomes

http://grabperf.org/scatter.php?test=277&hours=2

I apologize for the confusion that this may cause, but in the long run, this will help me make the code better, and more robust.

I have been using Skype as a landline pretty exclusively for the last 6 months, but the quality of the service has been degrading rapidly. Today, I called Samantha from the office and she said it sounded like I was calling from inside a tin can.

So, on a recommendation from a co-worker, I am giving Gizmo a try. Pretty immediately, I noticed a quality improvement over Skype, and people on my conference calls said it was much better.

So, if you want to reach me, try spierzchala on Gizmo, or +1-508-635-4420.

And Skype, let me know when your quality improves.

Tags: Gizmo, Gizmo Project, sound quality, SIP, VOIP, Skype

This paper is an extension of the work done for another article that highlighted the performance benefits of retrieving uncompressed and compressed objects directly from the origin server. I wanted to add a proxy server into the stream and determine if proxy servers helped improve the performance of object downloads, and by how much.

Using the same series of objects in the original compression article[1], the CURL tests were re-run 3 times:

1. Directly from the origin server
2. Through the proxy server, to load the files into cache
3. Through the proxy server, to avoid retrieving files from the origin.[2]

This series of three tests was repeated twice: once for the uncompressed files, and then for the compressed objects.[3]

As can be seen clearly in the plots below, compression caused web page download times to improve greatly, when the objects were retrieved from the source. However, the performance difference between compressed and uncompressed data all but disappears when retrieving objects from a proxy server on a corporate LAN.

Instead of the linear growth between object size and download time seen in both of the retrieval tests that used the origin server (Source and Proxy Load data), the Proxy Draw data clearly shows the benefits that accrue when a proxy server is added to a network to assist with serving HTTP traffic.

	MEAN DOWNLOAD TIME
Uncompressed Pages
Total Time Uncompressed — No Proxy	0.256
Total Time Uncompressed — Proxy Load	0.254
Total Time Uncompressed — Proxy Draw	0.110
Compressed Pages
Total Time Compressed — No Proxy	0.181
Total Time Compressed — Proxy Load	0.140
Total Time Compressed — Proxy Draw	0.104

The data above shows just how much of an improvement is gained by adding a local proxy server, explicit caching descriptions and compression can add to a Web site. For sites that do force a great of requests to be returned directly to the origin server, compression will be of great help in reducing bandwidth costs and improving performance. However, by allowing pages to be cached in local proxy servers, the difference between compressed and uncompressed pages vanishes.

Conclusion

Compression is a very good start when attempting to optimize performance. The addition of explicit caching messages in server responses which allow proxy servers to serve cached data to clients on remote local LANs can improve performance to even a greater extent than compression can. These two should be used together to improve the overall performance of Web sites.

[1]The test set was made up of the 1952 HTML files located in the top directory of the Linux Documentation Project HTML archive.

[2]All of the pages in these tests announced the following server response header indicating its cacheability:

Cache-Control: max-age=3600

[3]A note on the compressed files: all compression was performed dynamically by mod_gzip for Apache/1.3.27.

One of the performance hits that the GrabPERF system has is the dynamic generation of the main page. The nature of the SQL calls and the underlying PHP makes it scale exponentially past a certain number of measurements.

Last night, Kevin Burton made a grand suggestion: generate a static page on a regular schedule.

Duh!

Today, I wrote the script that does this. The performance of the main page has adjusted accordingly.

Yikes!

UPDATE: Ian Holsman reminded that if I use cURL, I can use the exiting PHP to build the pages without a PERL script.

I. AM. AN. IDIOT.

Now, bedtime.

Technorati Tags: GrabPERF, Web+performance, PHP, MySQL, Dynamic+pages, Static+pages, HTML

I am still swamped at work, but I have a glimmer of space available to me, so I thought that I would drop by and let everyone know what’s happening.

We are well on our way to being ready for the trip to BC and Alberta that starts Monday (June 26). We have a dining room full of luggage, and have a lot of information concerning travelling with Miss Wiggles. It’s been nearly 3 years since I was “home” to Victoria, so it will be fun to scout out and see what’s changed since the last visit.

As a sidenote, if anyone in the Victoria, BC area wants to do a meetup while I am in town, I would be happy to attend — need some lovely beer from Swan’s or Spinnaker’s.

GrabPERF continues to chug along almost completely unmanaged. One tiny improvement I made to scatter plot is the only code change in months. If things settle down at work (not likely until we get an extra body in here to support me), I will be updating some of the measurement code and back-end systems. Until I have time to go through a formal review process, the system is in maintenance mode.

While I am on vacation, I will likely been able to write some more; lot’s of thoughts on IIS 5.0, Net Neutrality, Firefly, and other things that are deeply buried right now.

Technorati Tags: Victoria, BC, Alberta, Canada, Vancouver Island, GrabPERF

Usually I classify this sort of mail as complete nonsense, and delet it. But this one was such a classic, I had to post it.

The letter is from the new CEO of the joint Borland/Segue. He is announcing that he thinks that Segue and Borland customers will be able to find cool ways to use the products of this new company…at least, after I translate it, it seems like that is what he is TRYING to say.

…

This is a great move for both of our organizations as we come together to tackle what we all know to be a key development challenge and the biggest opportunity for our industry — software quality. Borland and Segue have long shared a common belief that the challenge of software quality reaches far beyond testing and QA. Together we will approach this issue holistically, providing value at each stage of the software delivery lifecycle.

Our focus now is on the development of a comprehensive Lifecycle Quality Management solution — bringing together our unparalleled process improvement expertise with proper skills training and a true end-to-end quality technology offering. Our goal is alignment of people, process and technology, proactively driving higher standards of software quality while systematically reducing costs associated with rework and maintenance.

While continuing to enhance Segue’s quality and application performance technologies, we will also focus on delivering even tighter linkage with Borland’s broad portfolio of Application Lifecycle Management technologies. As part of a complete solution, these technologies will address quality across the entire lifecycle, eliminating quality issues at the root cause.

…

Chaucer and Shakespeare just rose from the dead, and they are looking for the marketing people who wrote this.

Technorati Tags: Fight the bull, nonsense, marketing

Matt threw a bunch of hardware at Ping-O-Matic this morning.

I think this is an improvement.

UPDATE: Anecdotally, I know that Ping-O-Matic is faster, because Performancing is done so much faster now.

Technorati Tags: Ping-O-Matic, Pingomatic, GrabPERF, Web Performance

If anyone wants to know why I am proud of GrabPERF, this graph should give you a clue.

Every hour, an aggregated value is produced for every test url. Counting up the Geometric Mean aggregations on a daily basis, the growth line is pretty amazing.

Doing a rough calculation, the system has grown from testing 40 urls to testing 104 urls.

But the true scope of this growth can only be seen by looking at the number of data insertions into the raw data table on a daily basis.

Currently, with the four measurement agents (I turned down one of the Technorati agents today to relieve the strain on the database server), the system is handling nearly 300,000 data insertions a day. Not even in the same timezone with most of the major sites I measure, but when I think that this is a system that I designed, I am stunned. For an unfunded, not-for-profit, one-person effort, I am constant astounded by what this system can handle.

Other areas of note over the last year:

• The Technorati-donated servers can now easily hold 60 days of detail data on a robust enterprise grade system, in a real datacenter
• The basement datacenter is now closed
• The new interface was created specifically to allow the system to grow and easily accommodate new features
• People are now approaching me on a daily basis to have sites added, or to have data explained
• GrabPERF went from one measurement agent to five agents in four locations, including a location in Europe (Portugal)
• GrabPERF has been used in various places to serve as an indicator or motivator for performance improvement, including: Bloglines, Ping-O-Matic, Technorati, PubSub (1 and 2), Blogwise, and others.
• A number of corporate and individual sponsors have stepped forward to support our efforts in many different ways: money, servers, measurement locations, commentary and critiques

I know that I have said it many times in person, or online, but thank you all. Those of you who use and support GrabPERF are the ones who continue to motivate me to make this system better on a daily basis.

Keep those cards and letter coming.

Technorati Tags: GrabPERF, growth, Web Performance, analytics

The team at BlogFlux laid on some major performance improvements to their Mapstats service last night.

This is a fantastic improvement! I can’t wait to hear how they achieved it.

Technorati Tags: BlogFlux, MapStats, Web performance, GrabPERF