Some random GrabPERF link love from the Web.
Technorati hosting blog pageload timing service
Technorati Tags: GrabPERF
Some random GrabPERF link love from the Web.
Technorati hosting blog pageload timing service
Technorati Tags: GrabPERF
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:
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
I have noticed that GrabPERF has been responding increasingly more slowly as of late. Well, I believe that I have resolved the performance issue: I moved the Web component of GrabPERF off of the machine where the database is housed.
However, when I did this, I hit a really stupid issue that was the result of a legacy httpd.conf file directive.
As well as GrabPERF, I moved this blog, also a heavy HTTP | PHP user, onto the same Web server. Then, once I had seen the DNS propagate, I went to this blog….and got the GrabPERF homepage!
WTF!?!?!?!
Turns out that I was the victim of a REALLY dense mis-configuration, which I removed from the new Web server configuration file. I had buried the NameVirtualHosts directive in a VirtualHost container, which was not part of the new server’s config file.
Without the NameVirtualHosts directive set, the server happily responds to all incoming requests with the first VirtualHost it finds in the httpd.conf file, which in in this case was GrabPERF.
Once I solved this, and placed the NameVirtualHosts directive outside of all of the VirtualHost containers, the server began working perfectly.
I then went and retrofitted the secondary Web server.
If none of this makes sense, it’s ok. I am not feeling real lucid right now.
Technorati Tags: Apache, httpd.conf, virtual domains, web hosting
As a Web performance analyst, this is the sort of graph that melts your mind and makes you want to scream at the gods|goddesses to rain a plague of locusts on the offending System|Network|Web Site Administrators.
This is a classic display of the “run in circles, scream and shout” problem identification and resolution process.
One-half of the Opera Web servers at http://www.opera.com/ are not responding.
50%.
They have three separate public IP addresses, and it is clear that behind those IPs are many more NAT|VIP machines that respond to requests.
Did I mention that one-half of the machines at all three IP addresses are not responding to HTTP requests?
Has anyone at Opera noticed this?
Sometimes I feel like even the echoes aren’t listening anymore.
Technorati Tags: GrabPERF, Web performance, Opera, Opera Web browser, www.opera.com
Thanks to the efforts of Paul Querna, GrabPERF is the proud receiver of data from the San Francisco Ask.com measurement agent.
Thanks to the powers that be at Ask.com, and I look forward to seeing lots of good data in the future!
Technorati Tags: GrabPERF, Web Performance, Ask, Ask.com, Paul Querna
Ouch!
Likely it will be back soon.
Technorati Tags: blogs, Brad Feld, Web performance, GrabPERF
UPDATE: Brad’s blog is back…kinda
AJAX is an amazing bit of technology, and a boon to Web performance.
The question is, how do you accurately measure it?
Now, from the perspective of synthetic transaction measurement, AJAX destroys the foundational concept of the “Page”, as it is built on the concept of the “sequence”. “Pages” assume a whole new HTML document is loaded in each step, where a “sequence” simply tracks the specific flow of steps that the customer performs, regardless of whether they occur in a new HTML document or not.
In this respect, passive monitoring services currently have a distinct advantage over synthetic measurement, because they intrinsically track the sequence of event that a customer triggers, rather than the pages that are downloaded. I will not declare the death of synthetic Web performance measurement yet (my day job is with one the largest synthetic Web performance measurement companies); but the industry has to re-evaluate many of its core precepts.
AJAX is a technology that will definitely benefit from the blending of passive and synthetic performance measurement into a single usable stream of information that companies can act on. With this blend, companies can determine how their servers are responding, as well as what customers are doing, tracking the flow of business data in real-time.
What will be interesting to watch is how the synthetic measurement companies (including the one I work for) respond to this. One of the companies in our space says that they handle it now, but I have yet to see the results of their effort and how they really implement it in the field.
How are you and your team measuring the performance of your AJAX applications?
Technorati Tags: AJAX, Web performance, synthetic, passive, measurement
Or so it seems from this article!
Makes sense if you think of it. Only part of the page is updated, so less bandwidth is used. And if you compress that data as well, you save even more.
Maybe AJAX is not just a novelty.
UPDATE [Feb 17 2006]: Some great additional articles are showing up in the comments. The catalogue demonstration is very cool.
UPDATE [April 29 2022]: AJAX, in the form of Single Page Application (SPA) Frameworks won.
The Web APM Blog: So many tools, so small a budget
If not now, when? And is Web performance management an extra, or a necessity?
Technorati Tags: Web performance, APM
Copyright © 2024 Performance Zen
Theme by Anders Noren — Up ↑