{"push_id":992654273,"size":1,"distinct_size":1,"ref":"refs/heads/krad_blkcache","head":"a52eb1abfac0e253662583a99fa99a0cf3fa8574","before":"394562e68c379d7a300b4d397caeb7f8f96bc7e8","commits":[{"sha":"a52eb1abfac0e253662583a99fa99a0cf3fa8574","author":{"email":"d046245a5851310b17dbc43de443633846271935@fb.com","name":"krad"},"message":"The change makes the cache operate optimally for NVM and SSD. The changes are\nmade after testing the cache with the NVM samples from Intel.\n\nThe system can now write 1GB/s+, read 2+GB/s, and read-write 1.5GB/s-.5GB/s for\nNVM\n\nThe cache can continue operate well for SSDs.\n\nThe work includes:\n\n- Added a new ENV for cache that can support direct IO\n- Added provision in the code to control the IO size of writes, parallelism\n- Made the code optimal for both NVM and SSD by controlling the IO size and parallelism\n- Made the options more resilient from starting the cache that can deadlock due\n  to bad configuration\n- Cleaned up buffer re-sizing\n- Other minor changes\n\nTask: 9858073\nSubscribers: leveldb@","distinct":true,"url":"https://api.github.com/repos/facebook/rocksdb/commits/a52eb1abfac0e253662583a99fa99a0cf3fa8574"}]}