mirror of
https://github.com/Amulet-Team/leveldb-mcpe.git
synced 2024-11-21 15:45:18 +00:00
946e5b5a4c
Highlights ---------- Mmap at most 1000 files on Posix to improve performance for large databases. Support for more architectures (thanks to Alexander K.) Building and porting -------------------- HP/UX support (issue 126) AtomicPointer for ia64 (issue 123) Sparc v9 support (issue 124) Atomic ops for powerpc Use -fno-builtin-memcmp only when using g++ Simplify IOS build rules (issue 114) Use CXXFLAGS instead of CFLAGS when invoking C++ compiler (issue 118) Fix snappy shared library problem (issue 94) Fix shared library installation path regression Endian-ness detection tweak for FreeBSD Bug fixes --------- Stop ignoring FLAGS_open_files in db_bench Make bloom test behavior agnostic to endian-ness Performance ----------- Limit number of mmapped files to 1000 to improve perf for large dbs Do not delay for 1 second on shutdown path (issue 125) Misc ---- Make InMemoryEnv return a no-op logger C binding now has a wrapper for free (issue 117) Add thread-safety annotations Added an in-process lock table (issue 120) Make RandomAccessFile and SequentialFile non-copyable
15 lines
535 B
Plaintext
15 lines
535 B
Plaintext
ss
|
|
- Stats
|
|
|
|
db
|
|
- Maybe implement DB::BulkDeleteForRange(start_key, end_key)
|
|
that would blow away files whose ranges are entirely contained
|
|
within [start_key..end_key]? For Chrome, deletion of obsolete
|
|
object stores, etc. can be done in the background anyway, so
|
|
probably not that important.
|
|
- There have been requests for MultiGet.
|
|
|
|
After a range is completely deleted, what gets rid of the
|
|
corresponding files if we do no future changes to that range. Make
|
|
the conditions for triggering compactions fire in more situations?
|