Skip to content

R
rocksdb

kvdb / rocksdb
11 个月 前同步成功

通知 0
Star 0
Fork 0
R
rocksdb

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 15 11月, 2016 7 次提交
  3. 14 11月, 2016 3 次提交
    • J
      CSS issues are arising on the Github Pages side. Temp fix. · 425210cc
      由 Joel Marcey 提交于 
      Need to figure out why this is still happening that `relative_url` is
not prepending the right value at just random times.
      425210cc
    • Y
      Optimize sequential insert into memtable - Part 1: Interface · 1ea79a78
      由 Yi Wu 提交于 
      Summary:
Currently our skip-list have an optimization to speedup sequential
inserts from a single stream, by remembering the last insert position.
We extend the idea to support sequential inserts from multiple streams,
and even tolerate small reordering wihtin each stream.

This PR is the interface part adding the following:
- Add `memtable_insert_prefix_extractor` to allow specifying prefix for each key.
- Add `InsertWithHint()` interface to memtable, to allow underlying
  implementation to return a hint of insert position, which can be later
  pass back to optimize inserts.
- Memtable will maintain a map from prefix to hints and pass the hint
  via `InsertWithHint()` if `memtable_insert_prefix_extractor` is non-null.
Closes https://github.com/facebook/rocksdb/pull/1419

Differential Revision: D4079367

Pulled By: yiwu-arbug

fbshipit-source-id: 3555326
      1ea79a78
    • Y
      Optimize sequential insert into memtable - Part 2: Implementation · df5eeb85
      由 Yi Wu 提交于 
      Summary:
Implement a insert hint into skip-list to hint insert position. This is
to optimize for the write workload where there are multiple stream of
sequential writes. For example, there is a stream of keys of a1, a2,
a3... but also b1, b2, b2... Each stream are not neccessary strictly
sequential, but can get reorder a little bit. User can specify a prefix
extractor and the `SkipListRep` can thus maintan a hint for each of the
stream for fast insert into memtable.

This is the internal implementation part. See #1419 for the interface part.
See inline comments for details.
Closes https://github.com/facebook/rocksdb/pull/1449

Differential Revision: D4106781

Pulled By: yiwu-arbug

fbshipit-source-id: f4d48c4
      df5eeb85
  5. 13 11月, 2016 3 次提交
  7. 12 11月, 2016 1 次提交
  9. 11 11月, 2016 5 次提交
  11. 10 11月, 2016 6 次提交
  13. 09 11月, 2016 5 次提交
  15. 08 11月, 2016 6 次提交
  17. 06 11月, 2016 2 次提交
    • A
      Java API - Implement GetFromBatch and GetFromBatchAndDB in WBWI · 24bceb09
      由 Adam Retter 提交于 
      Summary:
Needed for working with `get` after `merge` on a WBWI.
Closes https://github.com/facebook/rocksdb/pull/1093

Differential Revision: D4137978

Pulled By: yhchiang

fbshipit-source-id: e18d50d
      24bceb09
    • A
      Insert range deletion meta-block into block cache · 815f54af
      由 Andrew Kryczka 提交于 
      Summary:
This handles two issues: (1) range deletion iterator sometimes outlives
the table reader that created it, in which case the block must not be destroyed
during table reader destruction; and (2) we prefer to read these range tombstone
meta-blocks from file fewer times.

- Extracted cache-populating logic from NewDataBlockIterator() into a separate function: MaybeLoadDataBlockToCache()
- Use MaybeLoadDataBlockToCache() to load range deletion meta-block and pin it through the reader's lifetime. This code reuse works since range deletion meta-block has same format as data blocks.
- Use NewDataBlockIterator() to create range deletion iterators, which uses block cache if enabled, otherwise reads the block from file. Either way, the underlying block won't disappear until after the iterator is destroyed.
Closes https://github.com/facebook/rocksdb/pull/1459

Differential Revision: D4123175

Pulled By: ajkr

fbshipit-source-id: 8f64281
      815f54af
  19. 05 11月, 2016 2 次提交