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
The library already releases GIL so can be used with threading. It would be nice to have asyncio support as well, to avoid the need for all the extra threading layers for applications where that makes sense.
I'm imagining you would specify a thread pool size which zstd will use internally, akin to how you have a thread pool for the multithreaded compression option. Then the async compress/decompress methods would be run on that threadpool behind the scenes. So similar to how other async libraries work, where they might have a connection pool handling the async calls in the background.
At the very least, if there isn't support for async compression ops, there could be support for async reads/writes. E.g. where stream_writer feeds into aiofile.
The text was updated successfully, but these errors were encountered:
The library already releases GIL so can be used with threading. It would be nice to have asyncio support as well, to avoid the need for all the extra threading layers for applications where that makes sense.
I'm imagining you would specify a thread pool size which zstd will use internally, akin to how you have a thread pool for the multithreaded compression option. Then the async compress/decompress methods would be run on that threadpool behind the scenes. So similar to how other async libraries work, where they might have a connection pool handling the async calls in the background.
At the very least, if there isn't support for async compression ops, there could be support for async reads/writes. E.g. where stream_writer feeds into aiofile.
The text was updated successfully, but these errors were encountered: