As you mention, the only thing that matters is the end user's perspective. IT organizations are attacking these problems with tools from every domain and each tool presents its own views/perspective, terminology and technical approach.
We need to rally behind the APDEX (www.apdex.org) initiative and work towards an apples to apples way of understanding the user's experience and application performance.
Doug
BSM/ITSM Blog: http://dougmcclure.net
Latest management headlines from Network World:
IBM, South Carolina work to boost enrollment in IT classes
Compuware updates IT project portfolio management tool
10 New Year's Resolutions for Your Business
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
APDEX makes sense in network analysis
Rather than just talking about the end users’ perspective, WildPackets is addressing it head-on by being the only network analysis software vendor to implement the APDEX approach, as suggested by Doug MClure in his comment. By leveraging the work of the APDEX initiative, WildPackets is able to identify each and every transaction that exceeds the threshold for end-user tolerance. These include real-world transactions, like how long it takes to download a web page or how long it takes to get a response from a corporate database. This is the measurement that matters to all of us as end-users, and APDEX allows us to derive, report and alert on what users are really experiencing.
it all depends on the user
The key word is "end user" -- what they experience the application to be is, ultimately, what the performance of the application.
What they consider good or what they consider frustrating is what it ultimately is.
The question becomes how do you measure and then do something actionable about it!
User, which user?
There are many kinds of users, the end-user, the company, another company using your services, even an organization and departments. Each has different requirements, different effect to systems and "user" satisfaction, etc. And then there is the most important "user" - the business (and profit) goals of you company!
So - not so simple! APDEX is one way to formalize the performance measurement but.. Asking an "application" performance is a little too wide question today - previously an application was just maybe "one" program running or a bunch of transactions. Today an application touches (most of the time) several parts of the whole infrastructure and that's where the problem starts.
Too many companies still live without (business) capacity planning or really don't understand what it means. They just run performance numbers, try to speed up one part of the whole and often end up even worst problems they had previously.
Yes, most important is the "user" but, as in computers, priority alone can not be used for performance management because nobody has unlimited resources. Yes, like largest companies, simulations and tests can be done, but how many know how? Technically the most important, I think, is not to corner yourself without plan B. If usage performance would be easily predicted we could do the same with stock and start trading futures.
Post new comment