Dmitry, What we've discussed so far in this topic is essentially the same concept. We will deduplicate same byte sequences on page level.
On Fri, Nov 10, 2017 at 6:10 PM, Dmitry Pavlov <dpavlov....@gmail.com> wrote: > Hi Igniters, > > What do you think about implementing analogue of Java G1 collector featue > 'String deduplication': -XX:+UseG1GC -XX:+UseStringDeduplication > > Most of business application has almost all objects of type String. As > result char[] array is often on top of heap usage. To reduce consumption by > duplicates G1 collector in background identifies and deduplicates strings > having equal array into one instance (as String is immutable). > Unfortunately we can’t reuse collector’s feature as Ignite stores data > off-heap. > > What if we consider implementing same deduplication feature for Ignite > Durable Memory? > > Sincerely, > Dmitry Pavlov > > > ср, 18 окт. 2017 г. в 18:52, daradurvs <daradu...@gmail.com>: > > > Hi, Igniters! > > > > Are there any results of researching or a prototype of compression > feature? > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >
