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
When looking at CPU profiles, block decompression during reads, and compressing writes, show up significantly. On the read side, it would be nice for that decompression to take place asynchronously via some sort of read-ahead mechanism. On the write side, it would be nice for the compression to take place asynchronously and not block further compaction work. There is a PR in RocksDB that adds a pipeline for the compression side. We should investigate doing something similar.
The text was updated successfully, but these errors were encountered:
When looking at CPU profiles, block decompression during reads, and compressing writes, show up significantly. On the read side, it would be nice for that decompression to take place asynchronously via some sort of read-ahead mechanism. On the write side, it would be nice for the compression to take place asynchronously and not block further compaction work. There is a PR in RocksDB that adds a pipeline for the compression side. We should investigate doing something similar.
The text was updated successfully, but these errors were encountered: