Skip to content
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.

Evaluate optimizability of internal EnumSet #401

Open
alicederyn opened this issue Jan 25, 2019 · 1 comment
Open

Evaluate optimizability of internal EnumSet #401

alicederyn opened this issue Jan 25, 2019 · 1 comment
Labels
analysis Issue requiring analysis to determine severity

Comments

@alicederyn
Copy link
Collaborator

Allocating objects in hot loops can cause unwanted GC and memory pressure if the JVM cannot optimize them away with escape analysis. We use an EnumSet (to store which properties remain unset) versus bitwise operations for readability, but we could achieve similar readability by moving the bitwise logic into the generated Property enum, if there is any benefit.

@alicederyn alicederyn added the analysis Issue requiring analysis to determine severity label Jan 25, 2019
@alicederyn
Copy link
Collaborator Author

This would have to be done with a microbenchmark library like https://github.com/alicep-org/benchmark

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
analysis Issue requiring analysis to determine severity
Projects
None yet
Development

No branches or pull requests

1 participant