线程池的用法


除显式同步的 API 之外,所有 zlib API 均使用 libuv 的线程池。 这可能会在某些应用程序中产生意外的效果,例如性能不佳(可以通过调整池的大小来缓和)和/或无法恢复的灾难性内存碎片。

All zlib APIs, except those that are explicitly synchronous, use libuv's threadpool. This can lead to surprising effects in some applications, such as subpar performance (which can be mitigated by adjusting the pool size) and/or unrecoverable and catastrophic memory fragmentation.