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

Better support for short strings in Neo4j

When importing the OpenStreetMap data for Germany, with this feature in place we found that the DynamicStringStore was now 80smaller than before! Not only that but time for reading and writing strings had improved by at least 25! (the benchmark I got this from creates nodes and relationships as well, so pure string operations is probably even faster)

Disk space and RAM getting cheaper doesn’t mean you should waste it.

Redis is also obsessed with optimizing the space used by its data structures. HBase is recommending using LZO compression.

Original title and link: Better support for short strings in Neo4j (NoSQL databases © myNoSQL)

via: http://journal.thobe.org/2011/02/better-support-for-short-strings-in.html