Are We Killing The Web?
This is a fairly short piece about what I am seeing happening in browsers and how, in some cases, it is killing performance. First a little background or context, since 1999 I have been actively involved, almost 100% involved in performance tuning and troubleshooting Java servers, I was proxied in via my development environment of choice, ColdFusion. My work, since then, has been almost exclusively web based, including of course, databases, networks etc. So over the past 14 years I have used pretty much every browser that has been out there. With that in mind and having had hundreds of clients with thousands of applications I feel I have enough experience to state the bad news, things are getting worse at the browser end; the user end. That manifests itself in two ways, firstly performance and secondly, functionality oh and of course there is the aspect of application-browser specificity.
One thing that I see, very directly, is what happens when I record load-test scripts. As another note, I have pretty much moved away from using the Paessler Web Server Stress Tool to JMeter. The main reason for that is the increasing use of Ajax, JSon and similar constructs which place some of what was done at the server end, in the browser. JMeter is much better at capturing this. I have had two recent clients with almost the same "problem"; from their perspective, they did not have a problem. This is what I saw, in one client case, a single click in the browser caused the application to process 57 requests, in the other client case it was 33, this is not good particularly, as most of those requests were actually call-outs to other web sites with all the delays in response that this can and does cause. This is bad practice and really something to watch out for in new application design and this really needs to be avoided.
I disabled comments here so if you have any please email me go2riamb AT gmail DOT com