Can any one please share their experience on
“When do we make a call to use between Synchronised method and Synchronised Block”
Any Performance Issues?
Can any one please share their experience on When do we make a call
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Can any one please share their experience on
“When do we make a call to use between Synchronised method and Synchronised Block”
Any Performance Issues?
If you want to lock for the duration of a method call AND you want to lock on
this(or the current class, for astaticmethod), thensynchronizedmethods are the right solution.If you are locking on something else (e.g. a private lock object or some internal data structure), then the synchronized block approach is better.
Similarly, if only some of the code in a procedure call needs to be done holding a lock, it is better to use a synchronized block and put just that code in the block.
None, apart from the general principal that it is a bad idea to hold a lock longer than you need to. (The longer a lock is held, the more likely it is that other threads will need to wait.)