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

ConcurrentLinkedHashMap --> Caffeine when Java-8 based #2

Open
ben-manes opened this issue Apr 11, 2015 · 3 comments
Open

ConcurrentLinkedHashMap --> Caffeine when Java-8 based #2

ben-manes opened this issue Apr 11, 2015 · 3 comments

Comments

@ben-manes
Copy link

When transitioning to requiring Java 8, please upgrade to Caffeine. The performance should be relatively the same and the per-instance memory usage should be smaller.

ConcurrentLinkedHashMap changes will continue to be minimal, even more so now, and driven by requests from Java 6 users unable to upgrade. Caffeine is ideally the upgrade path for Guava cache users too, which due to Android cannot be significantly modified.

@ukclivecox
Copy link
Contributor

Thanks for the info. Certainly be good to test Caffeine as a replacement and see if it helps in load tests when we move to Java 8.

@ben-manes
Copy link
Author

If you upgrade from 1.2 to 1.4.2 you'll have much better cache performance, about the same as Caffeine. From there the benefit of upgrading will be better memory management and many more features.

@seldondev
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants