SCM command line metronome

Authors: PerformanceTroubleshootingTeam
Build basis: RTC 4.0.x

To measure the execution time of the SCM command line application, you can activate debug options on the command line.

Preparing

  1. Create a file called ".options" containing this text:
    com.ibm.team.filesystem.cli.core/debug=true
    com.ibm.team.filesystem.cli.core/debug/trips=true
  2. Save the file in the directory where you installed the scm command line, for example:
    C:\IBM\TeamConcert401\scmtools\eclipse

Tracing

  1. Launch the command scm -debug .options [scm commands and options]
  2. Example:
    C:\IBM\TeamConcert401\scmtools\eclipse>scm -debug .options list projectareas -r https://ibm-oprsurvfat7.ams.nl.ibm.com:9443/ccm/
    Start VM: C:\IBM\TeamConcert401\jdk\jre/bin/java.exe
    .....
    Debug options:
        file:/C:/IBM/TeamConcert401/scmtools/eclipse/options.txt loaded
    Time to load bundles: 3
    Starting application: 377
    (1000) "CCMProject1"
    Service Trip Statistics:
    Interface/method           Calls  Time
      IRepositoryRemoteService     1  24ms
        fetchOrRefreshItems        1  24ms
      IQueryService...........     1  19ms
        queryItems                 1  19ms
    -- Total time in service calls: 43ms

For further reference

Related topics:

Contributors:

Comments

Warning: Can't find topic Deployment.SCMCommandLineMetronomeComments

This topic: Deployment > WebHome > DeploymentTroubleshooting > PerformanceTroubleshooting > RTCClientPerformance > SCMCommandLineMetronome
History: r5 - 2013-05-02 - 12:59:16 - Main.lziosi
 
This site is powered by the TWiki collaboration platformCopyright © 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.