For those considering TT:<p>* Do not use Tokyo Tyrant in a production setting without replication. Make frequent backups.<p>* as far as I can tell, you have to call sync manually.. if you don't and the writes fill up your memory, writes slow to a crawl and there's a chance that the db file will corrupt when you finally sync or terminate the daemon.<p>* if you run out of disk space, your db will become corrupt<p>* if you accidentally start two instances of tokyo tyrant on the same file, it may become corrupt<p>* If you're using the hash db, be sure to tune the bnum param. If you're working with a lot of data, tune xmsiz as high as possible.<p>* 'putlist' stores duplicate records for b+ tree, which may or may not be what you expect.<p>* "bulk loading" the db is much much slower than mysql's select data infile
I really like the idea of being able to customize TC for whatever specific requirement is needed. That's something that most data stores are not very good at (and some may argue should not be good at), but it seems pretty powerful when it's there.