Issues for Android about replacing gzip using zstd

[yuanyetao]

Hi
I am attempting to use zstd in Android App to replace gzip.In Android,use zstd dictionary to uncompress data which is compressed in backend server.After serveral tests,i found that zstd dictionary uncompress slower than gzip.Gzip cost about 6ms but Zstd dictionary cost about 33ms.
Is the test result reasonable？Zstd dictionary uncompress slower than gzip？
I found some body run into the same question(facebook/zstd#501). Terrelln tried to run a build optimized with -0s and got decompressed faster than before. Shall we provide an android arr package which is built optimized with -0s ？

[luben]

Hmm, I was relying on the default optimization done by the NDK build, which is -O2. I think it's worth trying optimizing for size. I have just pushed a build change for it and will release it today so you can try.

[luben]

v1.5.0-4 has the optimized for size Android build. Can you try it?

[yuanyetao]

v1.5.0-4 has the optimized for size Android build. Can you try it?

Wonderful,i will try it in my app compared with the older version. The optimized result will feed back later.

[yuanyetao]

v1.5.0-4 has the optimized for size Android build. Can you try it?

We'v tried in Android. No optimized for uncompressing data in android devices.

[luben]

Hmm, strange, I have no idea what is the issue and how it can be better optimized.