graphite-dev team mailing list archive

[bobemoe <question225256@xxxxxxxxxxxxxxxxxxxxx>]

Question #225256 on Graphite changed:
https://answers.launchpad.net/graphite/+question/225256

    Status: Expired => Open

bobemoe is still having a problem:
Well, after a short break away from the project I'm back for a fresh
start.  Just thought I'd post my new finding in case anyone is having
similar issues, or the new info sparks some fresh ideas?!

So, fresh start with a new (class 10) SD card in the rPi.  Clean install
of everything.  Latest (Arch Linux) OS and firmware, and latest
Graphite/Carbon/Whisper.  But I'm still facing the same problem!  Things
do seem a little faster which I'm thinking is probably the improved SD
card (much less IO Wait), but we are still looking at 10secs (first
load) to even produce the /render endpoint "No Data" graph!

Some further research and digging has reviled what I think the problem
to be... Python on the ARM architecture is notoriously slow! Not the
answer I wanted but at least an answer, and there is a possible solution
or two:

PyPy is a python interpreter, aimed at improved performance.
Unfortunately not quite stable on ARM yet, and no binaries for Arch.
Compiling needs 2GB RAM which I don't have! Maybe I'll switch the OS to
Raspbian which does have binaries available.

There is also the option to pre-compile the python source to byte-code,
I'm not sure quite how to do that or how much impact it would have, or
even if it might already be done for/by Graphite?  Something to look
into.

Or maybe even swap out some of the rendering libs to C/C++ based code,
but I think we are into hacky territory here, unless anyone knows any
good drop-in replacements for any of the rendering components?

So, as before, any ideas on how to optimise for running on ARM would be
appreciated?

Cheers

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.