We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Detecting cache line can be memory and cpu intensive as it is now, involving reading (in-memory) files (in linux) or spawing new processes (on MacOS): in JCTools we save all of this via https://github.com/JCTools/JCTools/blob/a17b56f09cc9ec7d773707578c89f3ca9c11f968/jctools-core/src/main/java/org/jctools/util/PortableJvmInfo.java#L21
The text was updated successfully, but these errors were encountered:
@radcortez you can add more data about why is costy here, if you wish
Sorry, something went wrong.
radcortez
No branches or pull requests
Detecting cache line can be memory and cpu intensive as it is now, involving reading (in-memory) files (in linux) or spawing new processes (on MacOS): in JCTools we save all of this via https://github.com/JCTools/JCTools/blob/a17b56f09cc9ec7d773707578c89f3ca9c11f968/jctools-core/src/main/java/org/jctools/util/PortableJvmInfo.java#L21
The text was updated successfully, but these errors were encountered: