anchor.diff:  == Serialization
   
   Off-heap, disk and clustering need to serialize keys and values before storing them.
  -By default, the Java serialization is used.
  +By default, custom super-fast serializers are used for `Long`, `Integer`, `Character`, `Double`, `Float`, `byte[]` and
  +`String` objects.
  +A slightly faster, customized Java serialization is used for other object types.
   It is well-known for not being the fastest thing around.
   Ehcache uses it because it is supported out of the box.
  -However, you can increase performances by provoding your own serializers.
  +However, you can increase performance by providing your own serializers.
   
   == Copier
   
   By default, on-heap storage stores the entries by reference.
   You might want to use a copier to store entries by value for whatever reason.
  +Out of the box, Ehcache bundles a copier that makes use of its serialization mechanism:
  +`org.ehcache.impl.copy.SerializingCopier`.
   This can be much slower so watch out.
   
   == Loader-Writer
  
positive.code: 
  == Allocation rate
  
  Ehcache won't allocate any object during a simple `get()`.
  However, keep in mind that your configuration might do so.
  
  For instance, let's say you define an expiry policy like this.
  
negative.code: 
  == Stores
  
  We probably know that the fastest store is on-heap.
  Until you overwhelm the garbage collector.
  
  Your next best bet is off-heap.
  