Speed Tracer is a tool to help you identify and fix performance problems in your web applications. For more information and installation instructions, see the Speed Tracer documentation.
Profiling with Speed Tracer
Note: Profiling can be blocked by the Chrome extension security model, which can block requests made to the local filesystem. If you are using Chrome, make sure it is set to enable access to file URLs using the Chrome wrench Tools > Extensions menu and checking the Allow access to file URLs checkbox.
When you're ready to profile your web app, click the Profile Using Speed Tracer button:
The Speed Tracer dialog will appear, which allows you to select the project you want to profile. The project selected in the Package Explorer view or the Navigator view will be automatically selected in the dialog:
If necessary, the Google Plugin for Eclipse will perform a GWT compile of your app:
Automatically, a new Chrome tab will be created and load your application, and Speed Tracer will be started.
Note: Check the Speed Tracer FAQ if you run into trouble.
When you are done profiling, end the profiling session in Eclipse by clicking the Terminate Selected Launch button in the Development Mode view:
Jump to IDE
If a Speed Tracer trace contains a stack trace, clicking on a stack frame will jump to the line of code in Eclipse:
com.test.client.Test::$onModuleLoad will have Eclipse jump to that line of code:
Speed Tracer Settings
The settings for Speed Tracer for the Google Plugin for Eclipse are found in Window > Preferences > Google > Speed Tracer. The Speed Tracer Port is the port that the Google Plugin for Eclipse listens on for Speed Tracer requests.