anchor.diff:  we will often add a `net.openhft.chronicle.core.Jvm.safepoint` into the code because thread dumps are only reported at safe-points.
   
   
  -===== Summary
  +==== Summary
   
   In the test described above, the typical latency varied between 14 and 40 microseconds. The 99 percentile varied between 17 and 56 microseconds depending on the throughput being tested. Notably, the 99.93% latency varied between 21 microseconds and 41 milliseconds, a factor of 2000.
   
  
positive.code: Snapshots are available on https://oss.sonatype.org
  
  https://github.com/OpenHFT/Chronicle-Queue/releases[Chronicle Queue Release Notes]
  
  ===  Java Doc (3.6)
  see http://openhft.github.io/Chronicle-Queue/apidocs/
  
  == Simple Step-By-Step Guide
  see https://github.com/OpenHFT/Chronicle-Queue-Sample
  
negative.code: 
  IMPORTANT: This performance is not achieved using a *large cluster of machines*. This is using one thread to publish, and one thread to consume.
  
  ===  Java Docs
  see http://openhft.github.io/Chronicle-Queue/apidocs/
  
  === More benchmarks
  
  https://vanilla-java.github.io/2016/07/09/Batching-and-Low-Latency.html[Batching and Queue Latency]
  