Over the past few months, RebelLabs have been hard at work collecting data from over one thousand developers to collate a report focusing on Java performance and profilers. The team have grown increasingly interested in profiling recently, and have found it to be an intriguing area which many groups and developers do differently.

Whilst performance is something that can easily get drowned out by the day-to-day minutiae of meeting deadlines and just keeping systems running, RebelLabs write that it should be a priority for everyone. The reason for this? Well, when it comes down to it, performance is inextricably tangled up with your bottom line. As they put it, just a few millisecond delays on your site on prime shopping days “could be the difference between covering your body in gold lead or simply just leaves.”

Just so we’re all working off the same page, when RebelLabs refer to ‘performance,’ in this context, they define being performant as “increasing user response time and reducing latency in all parts of your system and as a whole, while being functionally accurate and consistent to your end user.” However, there are a myriad of other ways you might look at it – ranging from fixing immediate errors, to eliminating the need to jump through endless hoops.

When taking this into account, RebelLabs are largely concerned with the following Java performance considerations; CPU, memory, IO/ network, and database. In terms of performance, they’re taking into account throughput, responsiveness and latency, scalability, and resource consumption.

In the report, the team examine the various tools and techniques that enable Java developers to understand what’s going on with resources in their systems and how they are being used. Solutions examined include AppDynamics, New Relic, Plumbr, YourKit, JProfile, and of course in-house tool, XRebel.

One key factor RebelLabs are keen to impress however is that, for most developers, there’s no clean cut answer when it comes to selecting the best solution for a job. Depending on factors like architecture, design, where you’re at with your build, etc., there’s probably a whole arsenal of bullets to choose from.

If you’d like to read the whole report in full (as ever, it’s totally free), click here and get downloading.

 

 

What Does Java Performance Mean to You? And Why Does It Matter?

About The Author
- Editor of Voxxed.com, focusing on all things Java, JVM, cloud-y, methodical, future-fantastic, and everything in between. Got a piece of news, article or tutorial you'd like to share with your fellow Voxxians? Drop us a line at info@voxxed.com

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>