Linux and other operating systems
1. Install Java separately (see FAQ).
2. Unzip JetProfiler_linux_4.1.2.tar.gz to the desired folder (e.g. /usr/local/bin/jetprofiler or /home/USER/bin/jetprofiler).
3. Run ./JetProfiler
1. Generate load
Once you have installed Jet Profiler for MySQL, you can start collecting profiling information from your target database server. In order for this to be interesting, you need to be able to generate load on the target server. See FAQ for hints on generating load.
First, make sure you have set the correct user. Click on the left-most toolbar button to edit connection settings and enter the root user (or any other user with enough rights, see FAQ). Click Test connection to make sure it works.
Start recording by clicking the Record button. Depending on the load generated, it might take anything from a few seconds to a few minutes before you start seeing some results. We recommend recording at least 5 minutes.
Once you’ve recorded some data, you can start looking into the data collected. Here’s a description of the various parts of the Jet Profiler main window. (Please note that all features may not be available in some versions.)
The line chart
By clicking on different presets, you will see different data in the line chart. Some of them:
Threads - shows number of connections, number of running queries and number of slow queries are running.
Tables - shows the most frequently accessed database tables.
Users - shows the most frequent users.
You can also click on the line chart to select and zoom in areas of interest.
The lower section
The tabs show different top lists of the recorded data. Some of them:
Top Queries - shows the most frequent queries (the worst performing queries).
Top Tables - shows the tables that were most frequently accessed.
Top Users - shows the most frequent users.
If you can't seem to record anything, you can try polling more frequently. Adjust the polling interval in Recording settings (second toolbar button from left). Note that this comes with increased cost.
For more information, see the documentation.