You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, many CPU vendors support hardware accelerators to implement functions such as compression/decompression. Hardware accelerators can help offload the CPU so that the CPU can handle more computing tasks. In addition, hardware accelerators can provide higher throughput and lower latency due to their proprietary design. ZSTD 1.5.4 introduces the mechanism of an external sequence producer to help use the accelerator's capabilities, which is good. However, the application is currently required to make minor code changes (such as registering an external serializer with libzstd), which makes applications less willing to use this feature. Does the community consider going further to enable upper-layer applications to be insensitive without modifying any code? Just like OpenSSL, users can define their own providers.
looking forward to receive a reply, thanks very much.
The text was updated successfully, but these errors were encountered:
Currently, many CPU vendors support hardware accelerators to implement functions such as compression/decompression. Hardware accelerators can help offload the CPU so that the CPU can handle more computing tasks. In addition, hardware accelerators can provide higher throughput and lower latency due to their proprietary design. ZSTD 1.5.4 introduces the mechanism of an external sequence producer to help use the accelerator's capabilities, which is good. However, the application is currently required to make minor code changes (such as registering an external serializer with libzstd), which makes applications less willing to use this feature. Does the community consider going further to enable upper-layer applications to be insensitive without modifying any code? Just like OpenSSL, users can define their own providers.
looking forward to receive a reply, thanks very much.
The text was updated successfully, but these errors were encountered: