I don't understand this graph, any suggestion? Hahahaha

Ah, good ol' munin.

Don't look at latency unless figures spike waaay to high.

In fact, you'll probably need better tools for diagnosing latency anyway

In fact, just trash munin and learn to use prometheus with grafana.

@AndSoWeCode Is Munin too basic?

If I got the colors right, sometimes READ IOW is even higher than WRITE.That's weird bzc usually it's vice-versa - reads are cheaper to perform rather than writes.

Also.. a few dozens/hundreds ms IOW is also too high. 5ms, 10ms, maybe 15ms could be understandable. But hundreds? What's going on?

Is this cloud or your HW?

SAR graphs would be of much more use as they would provide all the context.

@netikras It's an instance on AWS.

@bettoisc you can't interact with munin. You're looking at images. You can't magnify. It's pretty much useless. Only good if you want to be alerted of something really bad. Otherwise it's old crap.

@AndSoWeCode That's true, munin doesn't let me interact with graph, I'll install the tool you just recommended to me and try some cool stuff.

@netikras The main context is: an odoo instance runing on a aws instance with 2 cpu and 4 ram. there are already multiple dbs.

@bettoisc it's not just installing. It has a learning curve, but once you got it, you'll never look at munin again.

@AndSoWeCode but how is that learning curve? Slow, fast, easy, hard...

@bettoisc a couple of days of fiddling is my guess. You know how it is now - new server software - it's a docker container, with an example setup script, zero documentation, go figure it out yourself.

But it is powerful, and widely used.