[Rock-dev] pocolog optimizations

Sylvain Joyeux

2014-06-11 16:22:08 UTC

Another tidbit of information: decompressing samples is a serious time hog.
Do not use compression if you can afford it AND need the performance.

I did not look into it further myself. I guess that we use a compression
level that is too high.

Sylvain

On Wed, Jun 11, 2014 at 3:18 PM, Sylvain Joyeux <bir.sylvain at gmail.com>

Post by Sylvain Joyeux
Hey. Given that I already did the work, I thought that someone would like
to pick it up.
During the pocolog-related discussion (or "bashing", call it however you
want), I profiled pocolog and found some very low-hanging fruits open for
optimization. I've published the result as a PR on github
https://github.com/rock-core/tools-pocolog/pull/1
This is NOT tested for correctness (in other words, it works on test
cases, but has not been fully tested). I won't take care of that, so feel
free to take it and try it. The pull request describes what kind of
performance enhancement ON POCOLOG you might expect. The rest of the
tooling staying untouched do NOT assume that you will get the same
improvement when running e.g. rock-replay
Sylvain

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.dfki.de/pipermail/rock-dev/attachments/20140611/01ff3222/attachment-0001.htm