anchor.diff:  To reduce the creation of the file handles, chronicle queue cashes them lazily and when it comes to writing data to the queue files, care-full consideration must be taken when closing the files, because on most OS’s a close of the file, will force any data that has been appended to the file, to be flushed to disk, and if we are not careful this could stall your application.
   
   '''
  -===== *Pretoucher and its configuration*
  +==== Pretoucher and its configuration
   
   `Pretoucher` is a class designed to be called from a long-lived thread. The purpose of the Pretoucher
   is to accelerate writing in a queue. Upon invocation of the `execute()` method, this object will pre-touch
  
positive.code: 
  *-* `BytesMarshallable` which is low-level binary, or text encoding.
  
  === [big]#User Guide#
  
  A Chronicle Queue is defined by `SingleChronicleQueue.class` that is designed to support:
  
  *-* rolling files on a daily, weekly or hourly basis,
  
  *-* concurrent writers on the same machine,
  
  *-* concurrent readers on the same machine or across multiple machines via TCP replication (With Chronicle Queue Enterprise),
  
  *-* zero copy serialization and deserialization,
  
  *-* millions of writes/reads per second on commodity hardware.
  
  Approximately 5 million messages/second for 96-byte messages on a i7-4790 processor.
  A queue directory structure is as follows:
  
  [source]
  ----
  base-directory /
     {cycle-name}.cq4       - The default format is yyyyMMdd for daily rolling.
  ----
  
  The format consists of size-prefixed bytes which are formatted using `BinaryWire` or `TextWire`.
  Chronicle Queue is designed to be driven from code. You can easily add an interface which suits your needs.
  
  NOTE: Due to fairly low-level operation, Chronicle Queue read/write operations can throw unchecked exceptions. In order to prevent thread death, it might be practical to catch `RuntimeException`s and log/analyze them as appropriate.
  
  Below, we first provide a section for quick reference to use Chronicle Queue. Then, in the next section we provide a more detailed guide.
  
  ==== [big]#Quick start#
  This section provides a quick reference for using Chronicle Queue to briefly show how to create, write/read into/from a queue.
  
  - Chronicle Queue construction
  
negative.code: * For more details see, https://vanilla-java.github.io/2016/03/24/Microservices-in-the-Chronicle-world-Part-2.html[Using Method Reader/Writers] and https://github.com/OpenHFT/Chronicle-Queue/blob/master/src/test/java/net/openhft/chronicle/queue/MessageReaderWriterTest.java[MessageReaderWriterTest]
  
  ''''
  ==== Detailed tracing of timings
  
  Chronicle Queue supports explicit, or implicit, nanosecond resolution timing for messages as they pass end-to-end over across your system.
  We support using nano-time across machines, without the need for specialist hardware.
  