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
Thursday, 15 March 2012
‹ Back

How to Make CouchDB (Feel) Faster

About:
,

A couple of tips and tricks from Martin ‘MC’ Brown that could help improve the CouchDB performance1:

Within CouchDB, there is a one-to-one relationship between the design documents that you create, and the indexes that are produced in the process.

Plus using stale views, updating views after and using the _changes feed.

  1. Or at least the perceived performance. ↩

Original title and link: How to Make CouchDB (Feel) Faster (NoSQL database©myNoSQL)

via: http://blog.safaribooksonline.com/2012/03/14/improving-couchdb-performance/