You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Seliverstov (JIRA)" <ji...@apache.org> on 2017/08/14 09:33:00 UTC
[jira] [Updated] (IGNITE-6049) Try to cache DataStreamer receiver
[ https://issues.apache.org/jira/browse/IGNITE-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Seliverstov updated IGNITE-6049:
-------------------------------------
Description:
Currently we send serialized DataStreamer receiver ({{StreamReceiver}}) in each {{DataStreamerRequest}}. It makes overhead on message deserialization time.
Also there is a default receiver, which is used in most of cases. As far as I understand It isn't necessary to send it since this instance is stateless.
Note: Improve future listeners model on update not to add the same listener to a future more than once ({{DataStreamerImpl.java:1410}})
was:
Currently we send serialized DataStreamer receiver ({{StreamReceiver}}) in each {{DataStreamerRequest}}. It makes overhead on message deserialization time.
Also there is a default receiver, which is used in most of cases. As far as I understand It isn't necessary to send it since this instance is stateless.
> Try to cache DataStreamer receiver
> ----------------------------------
>
> Key: IGNITE-6049
> URL: https://issues.apache.org/jira/browse/IGNITE-6049
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.1
> Reporter: Igor Seliverstov
>
> Currently we send serialized DataStreamer receiver ({{StreamReceiver}}) in each {{DataStreamerRequest}}. It makes overhead on message deserialization time.
> Also there is a default receiver, which is used in most of cases. As far as I understand It isn't necessary to send it since this instance is stateless.
> Note: Improve future listeners model on update not to add the same listener to a future more than once ({{DataStreamerImpl.java:1410}})
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)