Java-Thread-Affinity icon indicating copy to clipboard operation
Java-Thread-Affinity copied to clipboard

Bind a java thread to a given core

Results 17 Java-Thread-Affinity issues
Sort by recently updated
recently updated
newest added

As commented by @plusterkopp in #52, he created a [fork](https://github.com/plusterkopp/Java-Thread-Affinity) and added new features - need to review the fork and merge as appropriate

The fix for using -Daffinity.reserved with more than 64 core (#68) has an issue : to compute the bitset representing that mask, it uses under the hood Long.parseLong(substring, 16) where...

to reproduce run all test of /Users/teamcity/projects/Chronicle-Queue-Enterprise on m1 mac ``` [main/queue-cluster-1-replication-event-loop] WARN net.openhft.chronicle.threads.VanillaEventLoop - MediumEventLoop has been terminated due to exception java.lang.UnsatisfiedLinkError: /Users/teamcity/Library/Caches/JNA/temp/jna1914262682919037562.tmp: dlopen(/Users/teamcity/Library/Caches/JNA/temp/jna1914262682919037562.tmp, 1): no suitable image found....

Integrates Affinity with Chronicle Tune isolate configuration so that Affinity plays nicely with Tune out of the box. With this change, if isolate is installed and cores isolated only cores...

The tests were broken because Thread#toString includes thread ID on Java 21. Ignore this difference in toString presentation in the test cases fixes the issue.

bug

Appears to be an issue with compilation of the native affinity code on ARM via `g++`. Have reached out to Roger for comment, pointers.

bug
review