JProfiler Get rid of your performance problems and memory leaks! Modern Garbage Collection Tuning Java Performance Training Courses COURSES AVAILABLE NOW. We can provide training courses to handle all your Java performance needs Java Performance Tuning, 2nd ed The classic and most comprehensive book on tuning Java Java Performance Tuning Newsletter Your source of Java performance news. Subscribe now! Enter email: Training online Threading Essentials course JProfiler Get rid of your performance problems and memory leaks!

Back to newsletter 146 contents

When I started JavaPerformanceTuning.com more than 12 years ago, I recognised that the java performance tips were a valuable resource that needed extracting from articles and organising, but I didn't really give thought to organising the tools that I referenced. Last month's categoric publication of GC log analysis tools made me realise I need to organise the tools - especially given that I've referenced around 600 tools over the last 12 years!

A note from this newsletter's sponsor

So over this year I'll be categorising all the tools we've ever published including noting how long since they were last updated, which is useful to know in some cases (an old collection class is probably fine, whereas a tool that analysed JVM output in 2006 is probably not so useful now).

So on that vein, this month's categorised tool page is the GC log analysis tools from last month - easy given that they're already all categorised. Over the year, I'll aim to add categories for every type of tool I've referenced over the last 12 years.

Now on to all our usual links, including new tools, news, articles and, as ever, all the extracted tips from all of this month's referenced articles. Of note is the article by Patrick Peschlow which compares when you would want to use a ForkJoinPool rather than a ThreadPoolExecutor. Useful info in it's own right and I particularly liked the little gems of info like the way that unlike most other pools, the ForkJoinPool doesn't have a hard upper limit to it's pool size as it targets an active parallelism limit rather than a thread count limit.

A note from this newsletter's sponsor

News

Java performance tuning related news.

• comparison of access & update speeds of heap and native memory
• comparison of using memory mapped and non-memory-mapped techniques when processing data
• How eBay monitors logs, metrics and events from more than 500 TB/day of data flow
• WeakHashMap wasn't thread-safe for access, but is in Java 7 (see the reffed bug, and Doug Lea's delicious comment "It's a little weird making this class only a little thread-safe" - but he agrees it's worth it)
• Top 5 Advantages of SaaS-based Application Performance Management

Tools

Java performance tuning related tools.

• remote monitoring and management of the Java platform
• OpTier APM production environment transaction tracking and diagnostics
• concurrent trie-based map and set for long keys and values
• jbarrier - High performance barrier synchronization for Java
• Java-monitor - free, on-line monitoring service for various Java containers
• GC log analysis tools

A note from this newsletter's sponsor

Articles

• When Premature Optimization Isn't (Dustin Marx/marxsoftware)
• Scalability is Easy! (To Get Wrong) (Eli Weinstock-Herman/lessthandot)
• Three fundamental tricks for developers writing distributed systems (Pedro Belo/herokuapp)
• Efficient concurrent long set and map (Walter Bauer/Censhare)
• The fork/join framework in Java 7 (Patrick Peschlow/The H Developer)
• Best Practices for Load Testing Mobile Applications (Part I & II) (Steve Weisfeldt/neotys)

Jack Shirazi

Back to newsletter 146 contents