building_data_management_systems.Xuanzhou.2024Fall.DaSE
/
LevelDB-course-Lab
23
0
Разклонения 0
Код Задачи 0 Заявки за сливане 0 Версии 0 Уики Activity
小组成员：10215300402-朱维清 & 10222140408 谷杰
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53 Ревизии
1 Клон
1.7 MiB
ИН на ревизия: 299ccedfec
Клонове Маркери
${ item.name }
Create branch ${ searchTerm }
от '299ccedfec'
${ noResults }
LevelDB-course-Lab/TODO

13 lines
494 B
Директен файл Normal View История

Initial checkin. git-svn-id: https://leveldb.googlecode.com/svn/trunk@2 62dab493-f737-651d-591e-8d6aee1b9529
преди 13 години
​
​
​
​
​
​
​
​
​
A number of smaller fixes and performance improvements: - Implemented Get() directly instead of building on top of a full merging iterator stack. This speeds up the "readrandom" benchmark by up to 15-30%. - Fixed an opensource compilation problem. Added --db=<name> flag to control where the database is placed. - Automatically compact a file when we have done enough overlapping seeks to that file. - Fixed a performance bug where we would read from at least one file in a level even if none of the files overlapped the key being read. - Makefile fix for Mac OSX installations that have XCode 4 without XCode 3. - Unified the two occurrences of binary search in a file-list into one routine. - Found and fixed a bug where we would unnecessarily search the last file when looking for a key larger than all data in the level. - A fix to avoid the need for trivial move compactions and therefore gets rid of two out of five syncs in "fillseq". - Removed the MANIFEST file write when switching to a new memtable/log-file for a 10-20% improvement on fill speed on ext4. - Adding a SNAPPY setting in the Makefile for folks who have Snappy installed. Snappy compresses values and speeds up writes. git-svn-id: https://leveldb.googlecode.com/svn/trunk@32 62dab493-f737-651d-591e-8d6aee1b9529
преди 13 години
​
​
 
  1. ss
  2. - Stats
  3. 

  4. db
  5. - Maybe implement DB::BulkDeleteForRange(start_key, end_key)
  6.   that would blow away files whose ranges are entirely contained
  7.   within [start_key..end_key]?  For Chrome, deletion of obsolete
  8.   object stores, etc. can be done in the background anyway, so
  9.   probably not that important.
  10. 

  11. After a range is completely deleted, what gets rid of the
  12. corresponding files if we do no future changes to that range.  Make
  13. the conditions for triggering compactions fire in more situations?