[
https://issues.apache.org/jira/browse/IGNITE-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranas Baliuka updated IGNITE-6207:
-----------------------------------
Description:
It would be nice to have ability to keep buffer of mutable objects and reuse
objects as container for API.
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.
If feature is already available e.g. if {{streamer.keepBinary(true);}} forces
to take ownership of the object content without keeping reference please
provide guidelines got to achieve Low GC.
Thanks
P
was:
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.
> Low GC inserting bulk 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.
> 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.
> If feature is already available e.g. if {{streamer.keepBinary(true);}} forces
> to take ownership of the object content without keeping reference please
> provide guidelines got to achieve Low GC.
> Thanks
> P
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
