tree 0082f305a8677556f9930da98759e0dde856cc38
parent ac975d073a5a3c61f4dea2d8e0d3745d6a53b09c
author Jacek Centkowski <geminica.programs@gmail.com> 1657693131 +0200
committer Jacek Centkowski <geminica.programs@gmail.com> 1660321489 +0200

Add read/write metrics to TimedValueMarshaller

The following metrics were added:
* cache/chroniclemap/store_serialize_latency_<cache-name> the latency of
  serializing entries in chronicle-map store
* cache/chroniclemap/store_deserialize_latency_<cache-name> the latency
  of deserializing entries in chronicle-map store

Notes:
* metrics are not serializable hence as such they have to be transient
* in case 'readResolve' method is used instead of constructor fallback
  to metrics cache to get metrics; it is safe operation as store is
  created only after the TimeValueMarshaller is created for a cache in
  question hence metricsCache is going to have the corresponding entry

Change-Id: I195d83d4ebf351ad82925130d4e0c77231c3ec07