We would love to have some tests for this, too. We couldn't think of a way to assess the amount of CPU contention that would be reliable across test environments (CI, PR pre-checkin, debugging runs in GCP, local runs on dev machines, …). So we tested on my computer and watched CPU usage in Activity Monitor.
Would a few examples in the Javadocs suffice? Or perhaps a "test" class with fake tests (with the `@Test` annotation commented out so they don't actually run) to demonstrate uses? [ Full content available at: https://github.com/apache/geode/pull/2788 ] This message was relayed via gitbox.apache.org for [email protected]
