Edit
Attach
P
rintable
r2 - 2013-05-11 - 17:25:51 - Main.sbeard
You are here:
TWiki
>
Deployment Web
>
DeploymentMonitoring
>
JazzMetronomeToolKeepsUsHonest
<sticky><div id="container" > <div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/updated.png" alt="updated.png" width="50" height="50" align="right"> The Jazz metronome tool keeps us honest %DKGRAY% Authors: Main.DavidSchlegel <br> Build basis: Rational Team Concert 3.0.1.1 %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> From [[http://features.techworld.com/networking/2804/how-not-to-deploy-an-application-over-a-wan/][Techworld.com How not to deploy an application over a WAN]], Although the medical appointment application was advertised as being client/server based, it wasnt. In particular, the application was designed in such a way that the data in each field was sent character by character over the network. Hence, this was another example of an application that runs well over a LAN but presents performance problems over a WAN. ---++ Metronome tool We really wanted to avoid this with Rational Team Concert so we built a utility called the Jazz metronome to keep us honest. We wanted to make it easy to debug the client and find out when the server was being contacted (i.e. round-trips) and how long each server request took, so that we could easily see how chatty the client was being and fix the problem areas. The Jazz metronome was previously part of the Source Control developer tools plug-in and wasnt part of the Rational Team Concert client. But it turned out to be so useful that starting in the next milestone build following Beta 2 (M5, planned for late February), well be including the tool in the milestone downloads so that our customers and developers can easily use it. You can enable the Jazz metronome from the *Team > Jazz Source Control* preference page which will enable a trim widget that shows the global round-trip count, then you can open the detail window from the trim widget to get service by service breakdown as shown in the video at the end of this entry. <img src="%ATTACHURLPATH%/metronome-ui-2.png" alt="metronome-ui-2.png" width="515" height="245" /> The information displayed by the metronome tool is fairly low-level, it tracks which service and methods are called, the cumulative elapsed time in each request, and the slowest time. Whats also cool is that you can reset the counters and run something from the UI and see how chatty a particular feature is. With the service class grouping you can generally differentiate between work items, builds, process, or scm by looking at the service names. Were interested in your feedback and potential defects. To help you understand the information here are some usage hints: * If it aint broke if everything is running just fine then you can skip the rest of this blog entry and you never have to use the tool. * However, if you are stuck in a hotel with spotty connectivity and find the client sluggish, open the metronome window and take a peek at what is happening. * Turn off all background updating jobs in Team Central. Most of the query sections have a Resfresh option in their drop-down menu, while the build section has a configuration parameter for how often to contact the server. This will both help isolate who is being chatty and help reduce the round-trips while your connection is slow. * Open the metronome tool and re-run the action which you find is running too slow. Take note of the service calls. Since there are several factors that affect WAN performance, for example amount of data being sent or number of round-trips, [[http://en.wikipedia.org/wiki/Latency_%28engineering%29][latency]], its best to simply take notes and open a bug report. * If you can, include information in the bug report about your connection characteristics, ping time to the server, your [[http://www.speedtest.net/][connection speed]], and dont forget to copy and paste the tree shown in the metronome window directly into the bug report. This can be done by selecting the rows in the tree and clicking the Copy action in the bottom right. <img src="%ATTACHURLPATH%/metronome-ui1.png" alt="metronome-ui1.png" width="732" height="439" /> There are some service calls which are shared between all components. !TeamContentService is used to fetch and upload all content to and from the server. This method will be chatty when you load a repository workspace or upload work item attachements, so it will be more difficult to blame a particular component for being chatty. In many cases its ok to hit the server several times since we pipeline some calls and re-use the underlying http connection. This is why its best to interpret the information based on slowness of some operations and not only based on the round-trips in daily usage. Please, open metronome and start measuring away when things feel slow over a WAN. If the numbers look fishy, open a bug report (dont forget to look for duplicates first)! There are probably some embarrassingly chatty actions lurking out there, but wed rather know about them sooner rather than later so that we can fix them. Lets all work to make Rational Team Concert WAN friendly. Weve added another feature to the metronome tool which helps measure your connection speed to a Jazz server. This can help decide how responsive the client will be given the bandwidth and latency between the client and the server. <img src="%ATTACHURLPATH%/connection.png" alt="connection.png" width="616" height="546" /> ---+++++!! Related topics: [[JazzMon][JazzMon]], [[JazzMonFAQ][JazzMon FAQ]] ---+++++!! External links: * None ---+++++!! Additional contributors: Main.StevenBeard <sticky></div></div></sticky>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r5
<
r4
<
r3
<
r2
<
r1
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.