标签：
The answer is pretty simple -- use it when you actually need something it provides that synchronized doesn‘t,
like timed lock waits, interruptible lock waits, non-block-structured locks, multiple condition variables, or lock polling.
ReentrantLock also has scalability benefits, and you should use it if you actually have a situation that exhibits high contention,
but remember that the vast majority of synchronized blocks hardly ever exhibit any contention, let alone high contention.
I would advise developing with synchronization until synchronization has proven to be inadequate,
rather than simply assuming "the performance will be better" if you use ReentrantLock. Remember, these are advanced tools for advanced users.
(And truly advanced users tend to prefer the simplest tools they can find until they‘re convinced the simple tools are inadequate.)
As always, make it right first, and then worry about whether or not you have to make it faster.
标签：
原文地址：http://www.cnblogs.com/glf2046/p/4740568.html
