What do I gain by using the time-optimized encoder/decoder (TOED)? What do I lose?

Switching to the time-optimized encoder/decoder (TOED) will speed up the encoding and decoding procedures used by your application. In general, you can expect a 60% improvement in speed by switching from the space-optimized encoder/decoder to the time-optimized encoder/decoder.

However, since the time-optimized encoder decoder avoids calls to external library functions, the size of the object code and application executable is likely to be larger than when the space-optimized encoder/decoder (SOED) is used.

Additionally, the time-optimized encoder/decoder does not possess any tracing capabilities. Thus, during the development stage of your application, you are better off using the space-optimized encoder/decoder.

For more information about our runtime libraries, see the Runtime Choices section.

The samples included with some of the Knowledge Center answers are meant for your general understanding of the OSS products. Different versions of the products might produce slightly different outputs. Consult the products documentation and samples for the most up-to-date products information and code examples.