ISAR/libmdbx
3
0
Fork 0
mirror of https://github.com/isar/libmdbx.git synced 2024-10-30 11:29:19 +08:00
Code Issues Packages Projects Releases Wiki Activity

mdbx: fix README typos.

Browse Source
This commit is contained in:
Leo Yuriev 2018-03-21 14:10:03 +03:00
parent 475da5bcfe
commit 3c5cc40c77
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -233,7 +233,7 @@ scanning data directory.
Because of this syncing data to disk might be quite resource intensive and be main performance bottleneck Because of this syncing data to disk might be quite resource intensive and be main performance bottleneck
during intensive write workload. during intensive write workload.
> As compromise _libmdbx_ allows several modes of lazy and/or periodic syncing, including `MAPASYNC` mode, which modificate > As compromise _libmdbx_ allows several modes of lazy and/or periodic syncing, including `MAPASYNC` mode, which modificate
> data in memory and asynchronously syncs data to disc, moment to sync is picked by OS. > data in memory and asynchronously syncs data to disk, moment to sync is picked by OS.
> >
> Although this should be used with care, synchronous transactions in a DB with transaction journal will require 2 IOPS > Although this should be used with care, synchronous transactions in a DB with transaction journal will require 2 IOPS
> minimum (probably 3-4 in practice) because of filesystem overhead, overhead depends on filesystem, not on record > minimum (probably 3-4 in practice) because of filesystem overhead, overhead depends on filesystem, not on record
@ -339,7 +339,7 @@ Improvements over LMDB
This allows to minimize reclaim loop and make it execution time independent from total page count. This allows to minimize reclaim loop and make it execution time independent from total page count.
This results in OS kernel cache mechanisms working with maximum efficiency. This results in OS kernel cache mechanisms working with maximum efficiency.
In case of using disc controllers or storages with In case of using disk controllers or storages with
[BBWC](https://en.wikipedia.org/wiki/Disk_buffer#Write_acceleration) this may greatly improve [BBWC](https://en.wikipedia.org/wiki/Disk_buffer#Write_acceleration) this may greatly improve
write performance. write performance.
@ -378,7 +378,7 @@ Improvements over LMDB
9. Check if there is a row with data after current cursor position via `mdbx_cursor_eof()`. 9. Check if there is a row with data after current cursor position via `mdbx_cursor_eof()`.
10. Ability to explicitly request update of current record without creating new record. Implemented as `MDBX_CURRENT` flag 10. Ability to explicitly request update of present record without creating new record. Implemented as `MDBX_CURRENT` flag
for `mdbx_put()`. for `mdbx_put()`.
11. Ability to update or delete record and get previous value via `mdbx_replace()` Also can update specific multi-value. 11. Ability to update or delete record and get previous value via `mdbx_replace()` Also can update specific multi-value.
@ -419,7 +419,7 @@ Improvements over LMDB
22. Additional error code `MDBX_EMULTIVAL`, which is returned by `mdbx_put()` and 22. Additional error code `MDBX_EMULTIVAL`, which is returned by `mdbx_put()` and
`mdbx_replace()` in case is ambiguous update or delete. `mdbx_replace()` in case is ambiguous update or delete.
23. Ability to get value by key and duplicates count by `mdbx_get_ex()` 23. Ability to get value by key and duplicates count by `mdbx_get_ex()`.
24. Functions `mdbx_cursor_on_first() and mdbx_cursor_on_last(), which allows to know if cursor is currently on first or 24. Functions `mdbx_cursor_on_first() and mdbx_cursor_on_last(), which allows to know if cursor is currently on first or
last position respectively. last position respectively.