quickstep-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From navsan <...@git.apache.org>
Subject [GitHub] incubator-quickstep pull request #28: Add option to enable Google Profiling.
Date Sun, 12 Jun 2016 21:09:19 GMT
GitHub user navsan opened a pull request:


    Add option to enable Google Profiling.

    [Thanks @hbdeshmukh for the pointers on how to do this.]
    This PR makes profiling pretty easy. Steps to take: 
    * Install dependencies: Google Perftools must be installed already. This PR doesn't use
the third_party perftools. 
    * Build Quickstep with the ENABLE_GOOGLE_PROFILER flag turned on. You probably want to
use Build Type RelWithDebInfo. 
    * When running the CLI shell, pass the profiler_file_name flag to start profiling starting
from the second run of the query, and dump profile output to the file name specified. 
    * Alternatively, set the environment variable CPUPROFILE to turn on profiling for the
entire run (including first run, preloading, foreman and worker setup, etc.).
    * Use `google-pprof --dot profile.prof > profile.dot` or something similar to get a
usable output. 
    Tested with flag turned on and off, with RelWithDebInfo, with Clang on CloudLab machine.
Dependencies were pre-installed using `sudo apt-get install -y libgoogle-perftools-dev google-perftools`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/incubator-quickstep google_profiler

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #28
commit 7acd6434ddf335dd8c1a4ded562f5c6643fb1382
Author: Navneet Potti <navsan@apache.org>
Date:   2016-06-12T20:57:39Z

    Add option to enable Google Profiling.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message