Here is my code for this trial import. However what is quite Odd is Snappy is supposed to work much faster (from what i read) only the decompression is fast, but the compression takes longer.Īlso strangely smile is producing a longer persistable stringĬan anybody point out why or what I am doing wrong here?
Snappy is a compression library developed by Google. Smile compression time : 3314 microseconds Snappy compression is designed to be fast and efficient regarding memory usage, making it a good fit for MongoDB workloads. Smile (msgpack) Compression Trial compression percent : -24.561401 % Snappy de-compression to string time : 84 microseconds Snappy compression+convert to json time : 259549 microseconds If your disk can write 50 megabytes per second, you can get a frame rate of 12 fps. Pure saveable compression : 259490 microseconds Snappy Compression Trial compression percent : -22.807014 % Gzip de-compression to string time : 537 microseconds Gzip compression+convert to json time : 3477 microseconds Pure saveable compression : 3326 microseconds Here are my results Gzip Compression Trial compression percent : -8.7719345 % name, is compressed, its companion file name. The aim here is to compression entity JSON before persisting to REDIS. Write compressed files Do not use streaming compression with log files. compression, or compatibility with any other compression library instead, it aims for very high speeds and reasonable compression. Apache Kafka is unlike the typical traditional messaging systems. As more and more functionality gets supported by Kafka, the amount of data that flows through Kafka increases. I was trying to investigate what compression was suitable for my application for compression JSON string. Snappy is a compression/decompression library. Published JNowadays, Apache Kafka carries the lifeblood of an enterprise - its data or events.
0 kommentar(er)
