anchor.diff:  
   === What is the performance like?
   
  -While Vanilla and Index Chronicle support sub-microsecond latencies. If you use Wire the typical latencies tend to be around one micro-second.  You can still use raw writing of bytes if you need maximum performance.
  +While Single Chronicle (single file per cycle) supports sub-microsecond latencies. If you use Wire the typical latencies tend to be around one micro-second.  You can still use raw writing of bytes if you need maximum performance.
   
   === With a tight reader loop I see 100% utilization, will there be processing capability left for anything else ?
   
  
positive.code: 
  Chronicle works best in SEDA style event driven systems, where latency is critical and you need a record of exactly what was performed when. (Without expensive network sniffing/recording systems)
  
  === What is the performance like?
  While Vanilla and Index Chronicle support sub-microsecond latencies. If you use Wire, the typical latencies tend to be around one micro-second.  You can still use raw writing of bytes if you need maximum performance.
  
  === With a tight reader loop I see 100% utilization, will there be processing capability left for anything else ?
  
  Two approaches for reducing CPU usage are;
  
negative.code: what should the client do with the historical responses on startup?
  some heartbeat system so that client knows the server is alive
  archiving of the old queues (`VanillaChronicle` makes it easier at some cost).
  
  For more details on how to do this https://vanilla-java.github.io/2016/03/23/Microservices-in-the-Chronicle-world-Part-1.html[Read This series of posts]
  
  === What types of Excerpt are there?
  
  