Permalink
Browse files

update README.md

  • Loading branch information...
1 parent 48a7142 commit fdb3fb366ee1f410a509781b6f0e1dd96353a168 @frsyuki frsyuki committed May 15, 2010
Showing with 7 additions and 7 deletions.
  1. +7 −7 README.md
View
14 README.md
@@ -42,6 +42,13 @@ It measured performance of one server node using three client machines. Each cli
It measured performance of the cluster using 50 client machines. Each client machine gets 1,024,000 entries form the cluster using 32 threads.
+## Design
+
+<a href="http://kumofs.sourceforge.net">![Design of kumofs](http://kumofs.sourceforge.net/index/design.png)</a>
+
+**kumo-servers** store data and replicate them into other kumo-servers. **kumo-managers** watch life or death of kumo-servers and proceed automatic rebalancing when the number of kumo-servers is changed. **kumo-gatway** relay the requests from client applications to kumo-servers. Because kumo-gateway implements memcached protocol, you can use memcached client library to access kumofs.
+
+
## Installation
Following libraries are required to build kumofs:
@@ -64,13 +71,6 @@ Configure and install in the usual way:
$ sudo make install
-## Design
-
-<a href="http://kumofs.sourceforge.net">![Design of kumofs](http://kumofs.sourceforge.net/index/design.png)</a>
-
-**kumo-servers** store data and replicate them into other kumo-servers. **kumo-managers** watch life or death of kumo-servers and proceed automatic rebalancing when the number of kumo-servers is changed. **kumo-gatway** relay the requests from client applications to kumo-servers. Because kumo-gateway implements memcached protocol, you can use memcached client library to access kumofs.
-
-
## Example
This example runs kumofs on 6-node cluster. Run *kumo-manager* on **mgr1** and **mgr2**, *kumo-server* on **svr1**, **svr2** and **svr3**, then run *kumo-gateway* on **cli1**.

0 comments on commit fdb3fb3

Please sign in to comment.