greg/hanoidb
1
0
Fork 0
Code Issues 10 Pull requests 3 Projects Releases Packages Wiki Activity

Update README a bit

Browse source
This commit is contained in:
Kresten Krab Thorup 2012-04-24 14:06:54 +02:00
parent a8a66a43a0
commit 84f7fcc75b
1 changed files with 5 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -6,15 +6,12 @@ The storage engine can function as an alternative backend for Basho's Riak/KV.
Here's the bullet list: Here's the bullet list:
- Very fast writes and deletes, - Insert, Delete and Read all have worst case log<sub>2</sub>(N) complexity.
- Reasonably fast reads (N records are stored in log<sub>2</sub>(N) B-trees),
- Operations-friendly "append-only" storage (allows you to backup live system, and crash-recovery is very simple)
- The cost of evicting stale key/values is amortized into insertion, so you don't need to schedule merge to happen at off-peak hours. - The cost of evicting stale key/values is amortized into insertion, so you don't need to schedule merge to happen at off-peak hours.
- Operations-friendly "append-only" storage (allows you to backup live system, and crash-recovery is very fast)
- Supports range queries (and thus eventually Riak 2i.) - Supports range queries (and thus eventually Riak 2i.)
- Doesn't need a boat load of RAM - Doesn't need much RAM, but does need a lot of file descriptors
- All in 1000 lines of pure Erlang code - All around 3000 lines of pure Erlang code
Once we're a bit more stable, we'll provide a Riak backend.
### Deploying the hanoi for testing with Riak/KV ### Deploying the hanoi for testing with Riak/KV
@ -29,3 +26,4 @@ settings of the resulting dev nodes to use the hanoi storage backend.
1. `git clone git://github.com/basho/hanoi.git` 1. `git clone git://github.com/basho/hanoi.git`
1. `cd ..` 1. `cd ..`
1. `./deps/hanoi/enable-hanoi` # which does `make all devrel` 1. `./deps/hanoi/enable-hanoi` # which does `make all devrel`