anchor.diff:  
   Also, is there a reason these `1000` `gets` have be done serially in one thread? Why not submit `1000 get()` tasks to a pool of say `20` threads. Wouldn't this improve throughput and reduce latency?
   
  -== Answer
  +===== Answer
   
   The stateless client has been replaced with Chronicle Engine. The stateless client is not supported in ChronicleMap 3.x.  For  more information, please refer to Chronicle Engine FAQ's.
   
  
positive.code: 
  NOTE: Under high load, the Chronicle Map stateless client consolidates many small TCP requests into a single request when run with a number of threads.
  
  '''
  <<../ReadMe.adoc#,Back to ReadMe>>
  
negative.code: = Chronicle Map Frequently Asked Questions
  Neil Clifford, Peter Lawrey, Rob Austin, Jerry Shea
  :toc: manual
  :toclevels: 1
  :css-signature: demo
  :toc-placement: preamble
  :icons: font
  
  This document provides information for some common tasks within Chronicle Map.
  
  == Can I use Chronicle Map as a  replacement of `Redis`, with concurrency in mind?
  
  ===== Question
  
  I am investigating Chronicle Map as a potential replacement of `Redis`; with concurrency in mind.
  
  