After his recent benchmarking of Java 8 Streams, Nicolai Parlog is back to document suggestions from the community of other possible profiles. Parlog wants us all to remember that with Stream performance, numbers can lie.
Java performance is a hot topic at the moment and its Nicolai Parlog’s turn to get in on the action. He asks an important question of Java 8 Streams: can their performance really be that bad? Let’s get into investigating.
It’s really easy to misrepresent data, so its important to keep your performance percentiles in check. Alex Zhitnitsky shows us the Java performance metrics you need to follow for understanding how your application behaves in production.
With visitors demanding immediate response times, the fate of a website and the performance of APIs are becoming increasingly intertwined.
This year’s Developer Productivity Report chose to highlight Java performance and testing, finding that developers are happier, more productive and produce better quality code when performance testing is run during the coding process.
Alex Zhitnitsky is back to chat about java performance and debunking the stuff that you think you know about garbage collection. Read on for some serious trash-talking.
The performance tuning world is a dangerous place says Alex Zhitnitsky, who takes a look at how garbage collection affects java performance. Read on to understand what you’re up against, possible solutions and other alternatives available to you.
There are significant performance improvements to be made by writing software that works in harmony with underlying hardware, says technical problem solver Richard Warburton.
The eminent Martin Fowler recently wrote about the importance of not being afraid to bin old solutions and implement brand new architecture. Should IT architects leave old solutions or start fresh?
After two-year absence, JRockit Mission Control returns in Java 7u40 with support for HotSpot and more goodies.
Java EE 7 support and Orion improvements are on the menu for the open sources latest release train
Nikita Salnikov-Tarnovski recounts a nightmare twelve-hour search for the source of an applications memory leaks.