Munin VS VisualVM

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: almost 2 years 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

If you're curious, attach VisualVM and watch the RAM usage graph. You'll notice that Java performs garbage collections long before reaching allocating the maximum amount of RAM allocated, and you can't even feel any performance issue in-game. Source: 11 months ago

Hangs and deadlocks are significantly harder to debug. A first step is taking a thread dump so you can see what each thread in the JVM is currently trying to do. I like VisualVM for this, you can also use the command-line tools jps -l (to list all Java PIDs) and jstack for taking a thread dump. Source: 12 months ago

The Java VisualVM project is an advanced dashboard for Memory and CPU monitoring. It features advanced resource visualization, as well as process and thread utilization. - Source: dev.to / 12 months ago

This sounds like a server thread freeze/deadlock/crash or something. I think I would start debugging this using a tool like VisualVM; attach it to the game, wait for the hang, take a thread dump, and check what the server thread is up to. Source: about 1 year ago

Just wanted to chip in to say that /u/UtilFunction is correct. The proper way to measure memory consumption of any Java application independent of which garbage collector is used is to perform a heap dump (which automatically forces a complete garbage collection). I like to use VisualVM for that. Source: about 1 year ago