Current jcstress infrastructure is oblivious of CPU topology, and relies on luck to get the actors scheduled across/within interesting CPU packages, cores, threads. This can be done better by employing per-actor affinity, CPU topology parsing, and some combinatoric generators to cover all basic cases.
Work in progress:
https://github.com/openjdk/jcstress/compare/master...shipilev:affinity
Work in progress:
https://github.com/openjdk/jcstress/compare/master...shipilev:affinity
- relates to
-
CODETOOLS-7902884 jcstress: Fix new Sonar warnings
-
- Closed
-
- links to
-
Review openjdk/jcstress/30