rocksdb/docs/_posts/2014-04-07-rocksdb-2-8-release.markdown
Joel Marcey 3c2262400f Migrate the RocksDB Worpdress blog over to Jekyll
Summary:
Tried to:

- preserve existing links
- move existing images over (there were 2)
- preserve codeblocks (modified where apprporiate)
- etc.

Also as agreed upon:

- All blog posts are preserved.
- Comments are not preserved.
- Not turning on comments for future blog posts (use the FB developer group instead).
- Like button at the end of the blog post.

Depends on https://reviews.facebook.net/D63051

Test Plan: Visual

Reviewers: IslamAbdelRahman, lgalanis

Reviewed By: lgalanis

Subscribers: andrewkr, dhruba, leveldb

Differential Revision: https://reviews.facebook.net/D63105
2016-09-01 17:28:49 -07:00

1.5 KiB

title layout author category
RocksDB 2.8 release post icanadi blog

Check out the new RocksDB 2.8 release on Github.

RocksDB 2.8. is mostly focused on improving performance for in-memory workloads. We are seeing read QPS as high as 5M (we will write a separate blog post on this). Here is the summary of new features:

  • Added a new table format called PlainTable, which is optimized for RAM storage (ramfs or tmpfs). You can read more details about it on our wiki.

  • New prefixed memtable format HashLinkedList, which is optimized for cases where there are only a few keys for each prefix.

  • Merge operator supports a new function PartialMergeMulti() that allows users to do partial merges against multiple operands. This function enables big speedups for workloads that use merge operators.

  • Added a V2 compaction filter interface. It buffers the kv-pairs sharing the same key prefix, process them in batches, and return the batched results back to DB.

  • Geo-spatial support for locations and radial-search.

  • Improved read performance using thread local cache for frequently accessed data.

  • Stability improvements -- we're now ignoring partially written tailing record to MANIFEST or WAL files.

We have also introduced small incompatible API changes (mostly for advanced users). You can see full release notes in our HISTORY.my file.