github-repos/leveldb
1
0
Fork 0
mirror of https://github.com/google/leveldb.git synced 2025-03-28 12:10:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
kushal Singh Rathore 2019-10-07 07:52:20 +05:30 committed by GitHub
parent 62b322cc7d
commit 32ef77f9ba
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -145,8 +145,8 @@ update existing keys in the database.
Each "op" above corresponds to a write of a single key/value pair. Each "op" above corresponds to a write of a single key/value pair.
I.e., a random write benchmark goes at approximately 400,000 writes per second. I.e., a random write benchmark goes at approximately 400,000 writes per second.
Each "file sync" operation costs much less (0.3 milliseconds) Each "fillsync" operation costs much less (0.3 milliseconds)
then a disk seeks (typically 10 milliseconds). We suspect that this is then a disk seek (typically 10 milliseconds). We suspect that this is
because the hard disk itself is buffering the update in its memory and because the hard disk itself is buffering the update in its memory and
responding before the data has been written to the platter. This may responding before the data has been written to the platter. This may
or may not be safe based on whether or not the hard disk has enough or may not be safe based on whether or not the hard disk has enough