title: Hazelcast near cache - huge get latency
body: <p>There are 3 objects stored in my map - couple of MB each. They don't change so it makes sense to cache them locally at the node. And that's what I thought I was doing before I realized the average get latency is huge and that slows down my computations by large. See that hazelcast console:</p>
  
  <p><a href="https://i.stack.imgur.com/hH3rS.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/hH3rS.png" alt="Hazelcast console view"></a></p>
  
  <p>This makes my wonder where did it get from. Is it those 90 and 48 misses which I think  happend at first? The computations are run in parallel so I figure they could all issue a reguest to get before the entries were even cached and thus all of those would not benefit from near-cache at this point. Is it then some pre-loading method so that I would run it before I trigger all those parallel tasks? Btw. why entry memory is 0 even if there are entries in that near cache data table?</p>
  
  <p>Here is my map config:</p>
  
  <pre><code>&lt;map name="commons"&gt;
  
          &lt;in-memory-format&gt;BINARY&lt;/in-memory-format&gt;
  
          &lt;backup-count&gt;0&lt;/backup-count&gt;
          &lt;async-backup-count&gt;0&lt;/async-backup-count&gt;
          &lt;eviction-policy&gt;NONE&lt;/eviction-policy&gt;
  
          &lt;near-cache&gt;
  
              &lt;in-memory-format&gt;OBJECT&lt;/in-memory-format&gt;
              &lt;max-size&gt;0&lt;/max-size&gt;
              &lt;time-to-live-seconds&gt;0&lt;/time-to-live-seconds&gt;
              &lt;max-idle-seconds&gt;0&lt;/max-idle-seconds&gt;
              &lt;eviction-policy&gt;NONE&lt;/eviction-policy&gt;
              &lt;invalidate-on-change&gt;true&lt;/invalidate-on-change&gt;
              &lt;cache-local-entries&gt;true&lt;/cache-local-entries&gt;
          &lt;/near-cache&gt;
      &lt;/map&gt;
  </code></pre>
  
  <p><em>The actual question is why there are so many misses in the near cache and is it where that huge average get latency may come from?</em></p>