ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

tokyo cabinet: All content tagged as tokyo cabinet in NoSQL databases and polyglot persistence

Tokyo Tyrant / Tokyo Cabinet, un key-value store à la Japonaise (French)

Today is definitely the day of French NoSQL articles, this one being the second I’m posting already after NoSQL with HBase.

Lors d’un bench que j’ai effectué sur le produit, je me suis aperçu que le load average de mon serveur hébergeant Tokyo Tyrant et Tokyo Cabinet était anormalement élevé… Pas à cause du CPU, mais à cause du disque qui ne répondait pas assez vite aux I/O débités par la Tokyo Team… Pensez à bien choisir votre système de fichier dans ce cas (type – EXT3, XFS, … -, journalisé ou non, options de montage, …) et n’hésitez pas à mettre du RAID0, par exemple, pour optimiser les performances en lecture/écriture ou bien à répartir les écritures des différents fichiers physiques (données, ulogs, …) sur différents disques.

The above quote mentions the results of a benchmark showing some load caused not by CPU but by I/O and

For non-Frech readers, the article is an introduction to Tokyo Cabinet and Tokyo Tyrant. It makes repeated references to the Ilya Grigorik’s presentation: ☞ Lean & Mean Tokyo Cabinet Recipes (33min):

[Lua] is a mix of Ruby and Javascript… well, at least of the bad parts

@fredericfaure

via: http://decrypt.ysance.com/2009/12/tokyo-tyrant-tokyo-cabinet-key-value-store-japonaise/


Non-relational data stores for OpenSQL Camp

Igal Koshevoy has made available through Github his presentation on “Non-relational data stores for OpenSQL Camp: Overview, coding and assessment: MongoDB, Tokyo Tyrant & CouchDB”.

After a short presentation of the relational and non-relational worlds, Igal jumps to presented pros and cons for each of the MongoDB, Tokyo Tyrant and CouchDB, includes code snippets for all basic operations and completes with some benchmarking results. You can read the presentation embedded below (update: it looks like Google embed doesn’t work with this document or GitHub is not allowing access to it): so for the moment you can access it in PDF format ☞ here.


NoSQL: Distributed and Scalable Non-Relational Database Systems

NoSQL makes it in the Linux Magazine:

There’s an interesting shift happening in the world of Web-scale data stores. A whole new breed of scalable data stores is gaining popularity very quickly. The traditional LAMP stack is starting to look like a thing of the past. For a few years now, memcached has often appeared right next to MySQL, and now the whole “data tier” is being shaken up.

The article enumerates a couple of the solutions we came to become very interested in: Redis, Tokyo Cabinet, CouchDB, Riak, etc.

@fcatojo

via: http://www.linux-mag.com/cache/7579/1.html