You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Pranas Baliuka (JIRA)" <ji...@apache.org> on 2017/08/29 01:12:00 UTC

[jira] [Created] (IGNITE-6207) Low GC inserting of new entries

Pranas Baliuka created IGNITE-6207:
--------------------------------------

             Summary: Low GC inserting of new entries
                 Key: IGNITE-6207
                 URL: https://issues.apache.org/jira/browse/IGNITE-6207
             Project: Ignite
          Issue Type: New Feature
            Reporter: Pranas Baliuka


It would be nice to have ability to keep buffer of mutable objects and reuse objects as container for API.

Currently looks like there's no way to have a latch/flush checkpoint and forced to create new objects for Key/Value pair.

Proposed API e.g. {{forceAddOrReplace(Iterator<IPar<Key,Value>> entry)}} (or even better visitor pattern) where objects serialized but owners ship stays on client i.e. Ignite does not keep references to the objects provide between different itterator.next invocation. 

Clarification:
I know it sounds weird for enterprise developers (tolerant to extremely large latencies e.g. 100ms), but current system can not be practically applied for medium latency systems in finance.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)