[ 
https://issues.apache.org/jira/browse/IGNITE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958676#comment-15958676
 ] 

Vyacheslav Daradur commented on IGNITE-3592:
--------------------------------------------

[~vozerov]
As I understood that, the main goal of this task is to store data in compressed 
form.

This is what I need from Ignite as its user. Compression provides economy on 
servers.
We can store more data on same servers at the cost of increasing CPU 
utilization. 

I’m ready to discuss design of solution and public API. 
My thoughts:
1)      Compression at cache layer makes sense.
2)      Compression of annotated fields may be usefull already. (for example 
for large string fields)
3)      We need to use Deflater(ZLIB) compression library, it provides best 
compression ratio and C#.NET and C++ have its implementation.

I think will be better to continue discussion on dev list (сhoose better):
Initial: 
http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html
Second: 
http://apache-ignite-developers.2346864.n4.nabble.com/ignite-3592-is-ready-fo-review-Provide-some-kind-of-pluggable-compression-SPI-support-td15885.html


> 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.0
>
>
> 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.3.15#6346)

Reply via email to