Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Web Development

Real Users Really Matter


Step-by-Step, Putting It Together

Developers need a tool that measures the right service-level metrics and that can help them discover potential performance issues from a real user's perspective, with granularity down to individual transactions. By monitoring and tracing both synthetic and user-generated transactions while testing an application beta release, developers can proactively resolve issues that might impact production ramp up, including abnormalities with a low probability of occurrence but severe consequences. The actionable transaction performance information can also be utilized to tune the application and infrastructure so as to minimize the variability in response time over the entire spectrum of users. Finally, with the application in production, ITIL calls for continued optimization. A common tool that provides both the extensive transactional information required by developers and the scalability and low overhead of an operations tool is needed to facilitate cooperation and metadata transparency.

Table 1 summarizes the needs and requirements for cross-functional tools that can bridge the deployment phase of the ITIL application lifecycle with the operation and optimization phases, as well as the functional needs of developers during deployment, and the on-going 24/7 operations monitoring and problem resolution needs of operations personnel.

Conclusion

Applying an approach to monitor and diagnose performance problems from a real user's perspective during the deployment and operation phases of the application lifecycle can assure the performance of web application, and reduce the time to problem resolution in production. This approach offers data that can bridge the gap between development and IT operations, baking in performance preproduction, and offering an effective communication between development and operations to facilitate the resolution of performance issues to restore and optimize application performance.

Needs Functional Requirements
Direct measurement of end-user response time, especially for composite web applications Nonintrusive instrumentation of end-user browser for direct end-to-end performance measurement
Discover all real transactional paths through infrastructure and application Trace all real transactions from browser to back-end to the specificity of inside/outside firewall, tier, server, web service, and method/query level
Identify infrastructure and application bottlenecks Record and report time taken by each constituent element (whether infrastructure or application) to process transaction
Common platform for developers and operations personnel Record end-to-end transaction performance and tracing information, yet scalable with low-overhead for production use
Efficient workflow facilitating cooperation between functional groups: business, development, and operations Case-based workflow centered around business groups supported by extensive business-impact reporting
Table 1: Functional requirements


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.