-
Hi! The source data is my own customized mesh data. I found the data compressed by meshoptimizer is smaller than the original one, but after compressed by gzip, the compressed data becomes larger than the original one. Is this a common issue? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
This can sometimes happen; no compression scheme can guarantee monotonicity. That said, it's atypical. I would recommend checking if you observe the same result when using |
Beta Was this translation helpful? Give feedback.
-
I followed your advice in #383 (pad the normal data to 4 bytes), and the final data size (compressed by meshopt and gzip) is smaller than the original one (only compressed by gzip). Thanks for your great work! |
Beta Was this translation helpful? Give feedback.
This can sometimes happen; no compression scheme can guarantee monotonicity. That said, it's atypical.
I would recommend checking if you observe the same result when using
gltfpack
(-c
with or without gzip). Common issues that may prevent efficient compression are inefficient indexing, inefficient triangle order (for best results wrt compression size meshopt_optimizeVertexCacheStrip is recommended), and sometimes the use of floating point formats without filters can lead to complex compression size impact as well.