[lldb-dev] LLDB nightly benchmarks and flamegraphs

[Leonard Mosescu via lldb-dev]

+1, really nice. Any plans to add wall clock time? (I see you're using
perf, right?)

On Fri, Aug 3, 2018 at 3:59 PM, Zachary Turner via lldb-dev <
lldb-dev at lists.llvm.org> wrote:

> This is really cool.  Maybe you could do it for all of LLVM too?  It would
> be nice if, instead of cycling through each benchmark on a set interval,
> there were just a dropdown box where you could select the one you wanted to
> see.
>
> On Fri, Aug 3, 2018 at 3:37 PM Raphael Isemann via lldb-dev <
> lldb-dev at lists.llvm.org> wrote:
>
>> Hi everyone,
>>
>> I wanted to share a (hopefully useful) service for LLDB that I added
>> recently:
>>
>> If you go to https://teemperor.de/lldb-bench/ you'll now see graphs
>> that show the instruction count and memory usage of the last LLDB
>> nightlies (one per day). If you click on a graph you'll see a flame
>> graph that shows how much time we spent in each function when running
>> the benchmark. The graph should make it pretty obvious where the good
>> places for optimizations are.
>>
>> You can see all graphs without the slide show under
>> https://teemperor.de/lldb-bench/static.html.
>>
>> The source code of every benchmark can be found here:
>> https://github.com/Teemperor/lldb-bench If you want to add a
>> benchmark, just make a PR to that repository and I'll merge it. See
>> the README of the repo for instructions.
>>
>> I'll add more benchmarks in the future, but you are welcome to add your
>> own.
>>
>> Also, if you for some reason don't appreciate my amazing GNUplot
>> markup skills and prefer your own graphs, you can just grab the raw
>> benchmark data from here: https://teemperor.de/lldb-bench/data/ The
>> data format is just the time, git-commit and the
>> instruction-count/memoryInKB value (depending if it's a `.mem.dat` or
>> a `.inst.dat`).
>>
>> On a side note: Today's spike in memory is related to changes in the
>> build setup, not a LLDB change. I don't expect too many of these
>> spikes to happen in the future because the benchmark framework is now
>> hopefully stable enough.
>>
>> Cheers,
>>
>> - Raphael
>> _______________________________________________
>> lldb-dev mailing list
>> lldb-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20180803/c04764d9/attachment.html>