Munin VS Benchmark-ips

I rediscovered Munin. To my surprise it is written entirely in Perl. I remember Munin from years ago... It still seems healty and maintained and lies ready on your Deb-Repositories. So I followed the Easy Install Guide... Which really is easy, but fails to mention that you need to install your own HTTP-Server to serve the HTML-reports. Source: over 1 year ago

A bit of background, which may make understanding my choices in this lib easier: Munin is a resource monitoring tool using rrdtool, usually run in a Server/Client Setup. The client accepts plugins which are just executables in a directory. Usually written in a scripting language, but it actually doesn't matter. Data is fetched every 5 minutes, plugins are first run with a config argument to spit out a munin graph... Source: almost 2 years ago

Munin plugins and management script for monitoring various Pi-hole® statistics. Source: almost 2 years ago

When you do not have enough power you would get errors because looking up the plots would simply fail. Sounds more that there is one disk which is slower. I had one 2TB external usb which was really slow and the latency of lookups was through the roof. Are you on linux ? Then install munin-monitoring.org it shows latency of the disks out of the box. Source: about 2 years ago

What os ? On linux install https://munin-monitoring.org/ it will give you disk latency information. Source: about 2 years ago

We don't need to rely upon a priori reasoning only, we can use memory_profiles and benchmark_ips to compare the memory consumption and iterations per second of each solution. - Source: dev.to / almost 3 years ago

If specific implementation performance is a genuine concern for you, then you can benchmark it yourself and see! I recommend using benchmark-ips. Source: almost 3 years ago