Trust neither. The most optimal option I've found is webpagetest.org Its been quite handy lately. This tool does look interesting. Source: about 1 year ago

Webpagetest.org is another. Pagespeedinsights and lighthouse are great for identifying page load issues to fix, but actual page load times will always vary between the user and your web server. Universal analytics has some page load timings but that's going away soon and nothing afaik is in GA4. I've seen an example of building a page load timer in tag manager and dumping the results into an event. Source: over 1 year ago

So I am working on rebuilding our company's site with a new stack. I am running tests using webpagetest.org, and I am having trouble fully understanding the speed index results as well as the film strip view. The page renders quite fast everywhere I test it. Google Lighthouse shows it in the 90s + for performance score, however when I test the page on webpagetest, I get load times of 77 seconds (NOT MS) which is... Source: over 1 year ago

Webpagetest.org is great, and checking OP's site they have done an incredible job, I don't think I have ever made or seen an Ecom site this slick. Super clean waterfall view. Source: over 1 year ago

Thanks for the recommendation regarding webpagetest.org, another user made a similar recommendation so I will check it out. Source: over 1 year 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: about 1 year 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: about 1 year 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 / about 1 year 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: over 1 year ago