r7 - 2013-05-14 - 14:47:12 - StevenBeardYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > PerformanceTroubleshooting > RTCClientPerformance > SCMCommandLineMetronome

new.png SCM command line metronome

Authors: PerformanceTroubleshootingTeam
Build basis: RTC 4.0.x

Page contents

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

Related topics:

External links:

  • None

Additional contributors: LaraZiosi

Questions and comments:

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r7 < r6 < r5 < r4 < r3 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the 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.