Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Performance issue due to usage of synchronized java.util.TimeZone.getTimeZone(String) in CachedDateTimeZone #457

Closed
akarsh-jain opened this issue Dec 4, 2017 · 1 comment
Closed

Performance issue due to usage of synchronized java.util.TimeZone.getTimeZone(String) in CachedDateTimeZone #457

akarsh-jain opened this issue Dec 4, 2017 · 1 comment
Labels
Java8 RFE WontFix

Comments

@akarsh-jain
Copy link

Joda-Time Version: v2.3

Since java.util.TimeZone.getTimeZone(String) is synchronized, several concurrent calls to it through org.joda.time.CachedDateTimeZone.toTimeZone() (inherited from org.joda.time.DateTimeZone) get blocked. This creates a performance issue.

This can be rectified by overriding it with the non-synchronized java.util.TimeZone.getTimeZone(ZoneId). Pull request created for the same: #456
@jodastephen
Copy link
Member

Joda-Time is based on Java SE 5, so there probably isn't much that can be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Java8 RFE WontFix
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jodastephen @akarsh-jain