diff options
author | Enrico Granata <egranata@apple.com> | 2013-03-08 20:29:13 +0000 |
---|---|---|
committer | Enrico Granata <egranata@apple.com> | 2013-03-08 20:29:13 +0000 |
commit | f58cececaaee321143b177a0d7cbbffddcbfea4c (patch) | |
tree | a488537dcc777a7b1b68c3a35b1618d2f94850c1 /lldb/tools/lldb-perf/lib/Timer.cpp | |
parent | 8106d8082c406b4c381cd0d9604835fc35b45990 (diff) | |
download | bcm5719-llvm-f58cececaaee321143b177a0d7cbbffddcbfea4c.tar.gz bcm5719-llvm-f58cececaaee321143b177a0d7cbbffddcbfea4c.zip |
Initial checkin of a new project: LLDB Performance Testing Infrastructure
This is a very basic implementation of a library that easily allows to drive LLDB.framework to write test cases for performance
This is separate from the LLDB testsuite in test/ in that:
a) this uses C++ instead of Python to avoid measures being affected by SWIG
b) this is in very early development and needs lots of tweaking before it can be considered functionally complete
c) this is not meant to test correctness but to help catch performance regressions
There is a sample application built against the library (in darwin/sketch) that uses the famous sample app Sketch as an inferior to measure certain basic parameters of LLDB's behavior.
The resulting output is a PLIST much like the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
<dict>
<key>fetch-frames</key>
<real>0.13161715522222225</real>
</dict>
<dict>
<key>file-line-bkpt</key>
<real>0.029111678750000002</real>
</dict>
<dict>
<key>fetch-modules</key>
<real>0.00026376766666666668</real>
</dict>
<dict>
<key>fetch-vars</key>
<real>0.17820429311111111</real>
</dict>
<dict>
<key>run-expr</key>
<real>0.029676525769230768</real>
</dict>
</array>
</plist>
Areas for improvement:
- code cleanups (I will be out of the office for a couple days this coming week, but please keep ideas coming!)
- more metrics and test cases
- better error checking
This toolkit also comprises a simple event-loop-driven controller for LLDB, similar yet much simpler to what the Driver does to implement the lldb command-line tool.
llvm-svn: 176715
Diffstat (limited to 'lldb/tools/lldb-perf/lib/Timer.cpp')
-rw-r--r-- | lldb/tools/lldb-perf/lib/Timer.cpp | 47 |
1 files changed, 47 insertions, 0 deletions
diff --git a/lldb/tools/lldb-perf/lib/Timer.cpp b/lldb/tools/lldb-perf/lib/Timer.cpp new file mode 100644 index 00000000000..59871aab4ce --- /dev/null +++ b/lldb/tools/lldb-perf/lib/Timer.cpp @@ -0,0 +1,47 @@ +// +// Timer.cpp +// PerfTestDriver +// +// Created by Enrico Granata on 3/6/13. +// Copyright (c) 2013 Apple Inc. All rights reserved. +// + +#include "Timer.h" +#include <assert.h> + +using namespace lldb::perf; + +TimeGauge::HPTime +TimeGauge::now () +{ + return high_resolution_clock::now(); +} + +TimeGauge::TimeGauge () : +m_start(), +m_state(TimeGauge::State::eTSNeverUsed) +{ +} + +void +TimeGauge::start () +{ + m_state = TimeGauge::State::eTSCounting; + m_start = now(); +} + +double +TimeGauge::stop () +{ + auto stop = now(); + assert(m_state == TimeGauge::State::eTSCounting && "cannot stop a non-started clock"); + m_state = TimeGauge::State::eTSStopped; + return (m_value = duration_cast<duration<double>>(stop-m_start).count()); +} + +double +TimeGauge::value () +{ + assert(m_state == TimeGauge::State::eTSStopped && "clock must be used before you can evaluate it"); + return m_value; +} |