Slow on Raspberry pi 3?

[Robertbaelde]

Annyone tried running it on a raspberry pi 3? When i run a dashboard with +- 10 charts on a raspberry, it is really slow to boot up (around a minute) and when it boots, the clock for example updates only every 10 seconds. Is there something i might do wrong, that requires a lot of power from the raspberry? or is the dashboard simply heavy to run?

[antony]

I tend to run the dashboard on Now.sh/Heroku/AWS etc and just have a browser on the Pi. I've not noticed any issue at all - I too run on a Zero with -/+ 10 charts (browser only).

I don't believe the dashboard is particularly heavy to run though - I'd be interested in knowing why this is the case.

[Robertbaelde]

I can give you access to the git (bitbucket) of my configuration? Not sure how to debug this, as i'm not that familiar with node.

[antony]

Happy to take a look, sure.

I can run some metrics against it and see how heavy it is to run.

[Robertbaelde]

Greath, whats your bitbucket username? (you can also email me at robert@payless.events)

[antony]

I'm 'wirahx' on bitbucket

[antony]

Nice dashboard!

I'm doing some profiling on client/server for your dashboard (pm2/chrome profiling), so i'll update you with my findings when I've gathered enough data.

[antony]

Btw pretty important, how is your RPi configured?

You would probably want to give 64mb+ video memory to Chrome, as the chartist library, whilst light, might need a fair bit of rendering memory.

Is it just when you have a lot of charts?

Are you running the backend and the chrome browser on the same RPi?

[antony]

I'm still looking into this - I need a RPi to test against, so I'm prepping one of mine to help with this issue and another potential issue as soon as I can.

I run on a RPi zero (minus graphs) at work, and I've not noticed any slowdown, so it's possible that the chartist plugin is a bit heavier than I'd like it to be.