MiKandi Experiences with SDCH, a Demo and Thanks

[Christopher O'Connell]

Hello all,

First and foremost, many thanks for the insightful posts on this list. We found them invaluable as we implemented SDCH.

Second, as promised, our experiences with SDCH. https://mikandi.com/blog/tips-and-tricks/press-me-a-sdch-implementing-shared-dictionary-compression/

Finally, a few tools we use for working with dictionaries and an automated demo to train a dictionary on 10 random Wikipedia pages and then run a comparison on VCDiff, GZip and VCDiff+GZip on 20 random Wikipedia pages: https://github.com/mikandi/sdch-tools

All the best,

~ Christopher

[ernest.w....@gmail.com]

Hi Christopher,

Nice post!

Do you remember why did you resort to interleaved format (except partial decoding)? From few examples I've ran I saw that interleaved format gives worse gzip compression, and the final result is bigger.

[Christopher O'Connell]

I thought it was required. I'm not sure we tried it without. New test.

--
You received this message because you are subscribed to the Google Groups "SDCH" group.
To unsubscribe from this group and stop receiving emails from it, send an email to SDCH+uns...@googlegroups.com.
To post to this group, send email to SD...@googlegroups.com.
Visit this group at https://groups.google.com/group/SDCH.
For more options, visit https://groups.google.com/d/optout.

[ernest.w....@gmail.com]

nope, it is not required but suggested, if you use interleaved (at least this is how I understood it) you can decode partially transferred data, when it is not interleaved you have to have the whole data to decode. Chrome can handle both, at least this is what I see. Interleaved compression is not as good as standard format, at least in my test, OTOH this may be not true for your data