anchor.diff:  queue.dump();
   ----
   
  -4. Cleanup
  +- Cleanup
   
   Chronicle Queue stores its data off-heap, and it is recommended that you call `close()` once you have finished working with Chronicle Queue, to free resources.
   
  
positive.code: This is much more scalable than being limited to the amount of memory space that you have.
  You can buy a redundant pair of 6TB of enterprise disks very much more cheaply than 6TB of memory.
  
  * *15. File handles and flushing data to the disk*
  
  As mentioned previously Chronicle Queue stores its data off-heap in a ‘.cq4’ file.
  
negative.code: As Chronicle Queue doesn't partition its topics, you get total ordering of all messages within that topic.
  Across topics, there is no guarantee of ordering; if you want to replay deterministically from a system which consumes from multiple topics, we suggest replaying from that system's output.
  
  '''
  * *4. Tailers and file handlers clean up*
  
  Chronicle Queue tailers may create file handlers, the file handlers are cleaned up whenever the associated chronicle queue's `close()` method is invoked or whenever the Jvm runs a Garbage Collection.
  