This weekend brings another snapshot build. I’ve been working mainly on refactoring (exceptions hierarchy) and optimization of critical components like network connectivity, indexing and routing. After a few fixes performance has decreased to something like 80 TPS on one node. I was doing my best to work that out. Thankfully it’s been improved. Tests now run smoothly, all is lighter and more robust.
I have performed a benchmark with JMeter and results finally look promising. On a single node throughput was 659.2 TPS for put w/ Lucene indexing. 999 concurrent threads were storing 20 records. One thing is stability under such load that proves it must be sort of decent and another of course the result itself.
Uncategorized
I’ve just uploaded 0.2.2 snapshot build. What’s been done since the last weekend:
- caching aspect
- components/internal architecture redesigned
- serialization using JBoss-serialization library
- Java API
- replication logic implemented using consistent hash algorithm
- JGroups discovery added - from now on, data servers ping master and are noticed within the cluster
- tremendous amount of refactoring
Uncategorized
Revision 400 has been reached and what we’ve got here is:
- downloadable bundle that can be run on Windows and Linux
- sample scripts for PHP and shell CURL usage that can put records via HTTP interface
- support for two persistence mechanisms so far
- BerkeleyDB JE
- Files storage
- performance achieved on my box (local master and local data server): 196 TPS on record put with underlying BerkeleyDB persistence, 500 concurrent threads, logging on, Lucene indexing on
Uncategorized