[
https://issues.apache.org/jira/browse/IGNITE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084722#comment-16084722
]
Amit Pundir commented on IGNITE-3592:
-------------------------------------
[~vozerov] Compression support for the network messages would be greatly
appreciated. Our cluster is running on clouds on multiple data-centers and we
experience significant overhead in cross data-center calls from Ignite client
node to Ignite server node. The round trip time between the data-centers is
still reasonable (under 60 ms).
We are using partitioned cache and our values for the caches are big.
Compression for the network calls will help us a lot.
Besides that, we have also observed the following operations to take
significant amount of time -
1. org.apache.ignite.transactions.Transaction ==> commit ==> 2043 milli-seconds
2. org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi ==>
createTcpClient ==> 2042 milli-seconds
The above 2 timings suggest significant delay between server node to server
node communication also. Could you please help address these issues sooner than
2.2.
> Provide some kind of pluggable compression SPI support
> ------------------------------------------------------
>
> Key: IGNITE-3592
> URL: https://issues.apache.org/jira/browse/IGNITE-3592
> Project: Ignite
> Issue Type: Task
> Components: cache
> Reporter: Alexey Kuznetsov
> Assignee: Vyacheslav Daradur
> Fix For: 2.2
>
>
> It may be useful in some cases to compress data stored in cache.
> And in order to give access to compressed data from SQL engine this support
> should be implemented in ignite-core level.
> See discussion on dev-list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
