Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Alternative compression methods
See original GitHub issueIs your feature request related to a problem? Please describe.
I’m using Keyv to wrap connection with Redis and I would like to compress the content cached in Redis. This caching process is time-sensitive, so it should favour speed over compression rate. Thus why I’m atm using separate wrapper using snappy as the compression algorithm. I did performance tests and it turned out that Brotli in BROTLI_MIN_QUALITY mode is almost 2x slower than snappy!
So, the real problem for me is that Brotli is the built-in compression mechanism that cannot be easily changed for anything else.
Describe the solution you’d like
I would like to have some options if it goes to choosing the compression method that can be used with Keyv.
Describe alternatives you’ve considered
Atm I’m using custom kdybicz/apollo-server-snappy-cache-wrapper wrapped for Keyv.
Additional context
Scotty, We Need More Power!
Issue Analytics
- State:
- Created a year ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@alfaproject and @kdybicz we have merged in the changes and will be planning a release this week. Also, will add in support for snappy as a compression provider and most likely gzip.
Closing this issue as we have now published the compression changes. https://github.com/jaredwray/keyv/releases/tag/2022-09-02