The Artima Developer Community
Articles | News | Weblogs | Books | Forums
Artima Forums | Articles | Weblogs | Java Answers | News
Sponsored Link •

Java Buzz Forum
A Case Study in Analysing Latency: Lock vs Synchronized

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
justin cater

Posts: 19616
Nickname: justin78
Registered: Mar, 2011

Justin Cater is executive editor at Java Code Geeks
A Case Study in Analysing Latency: Lock vs Synchronized Posted: Aug 19, 2015 1:12 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by justin cater.
Original Post: A Case Study in Analysing Latency: Lock vs Synchronized
Feed Title: Java Code Geeks
Feed URL: http://feeds.feedburner.com/JavaCodeGeeks
Feed Description: Java 2 Java Developers Resource Center 		Latest Java Buzz Posts
Latest Java Buzz Posts by justin cater
Latest Posts From Java Code Geeks

Advertisement
In particular in this post we will discuss: Garbage created by java.concurrent.Lock Comparing Lock to synchronized How to measure latency programatically The impact of contention on Lock and synchronized The impact of co-ordinated omission on latency tests Back to one of my favourite topics garbage creation / allocation. See my previous posts (e.g. First rule of performance ...

Read: A Case Study in Analysing Latency: Lock vs Synchronized

Topic: Top 10 Useful, Yet Paranoid Java Programming Techniques Previous Topic   Next Topic Topic: RAM is the new SSD
Sponsored Links


Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use