SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code. SonarQube integrates into the developers' CI/CD pipeline and DevOps platform to detect and help fix issues in the code while performing continuous inspection of projects.
Supported by the Sonar Clean as You Code methodology, only code that meets the defined quality standard can be released to production. SonarQube analyzes the most popular programming languages, frameworks, and infrastructure technologies and supports over 5,000 Clean Code rules.
Trusted by 7 million developers and 400,000 organizations globally to clean more than half a trillion lines of code, Sonar has become integral to delivering better software.
Explore our pricing and request an evaluation: https://www.sonarsource.com/plans-and-pricing/
Based on our record, VisualVM seems to be a lot more popular than SonarQube. While we know about 21 links to VisualVM, we've tracked only 1 mention of SonarQube. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
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 / 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: about 1 year ago
Even for Java, C# and JS we do enforce such kind of rules, e.g. https://sonarqube.org. - Source: Hacker News / over 1 year ago
Eclipse Memory Analyzer - The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and over 350 open source projects, including runtimes, tools and frameworks.
Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.
JConsole - Provides information about performance and resource consumption for Java applications.
CodeClimate - Code Climate provides automated code review for your apps, letting you fix quality and security issues before they hit production. We check every commit, branch and pull request for changes in quality and potential vulnerabilities.
dotMemory - dotMemory allows users to analyze memory usage in a variety of .NET and .NET Core applications.
Checkmarx - The industry’s most comprehensive AppSec platform, Checkmarx One is fast, accurate, and accelerates your business.