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

Designing a MongoDB Schema for a Monitoring System

Rick Copeland describes the results of his experiment designing and testing a MongoDB-based monitoring system. Some of his findings are quite interesting:

  1. So documents that grow and grow and grow are a real performance-killer with MongoDB.
  2. BSON actually stores documents as an association list thus lookups are not constant-speed

One aspect that the post doesn’t cover is how MongoDB behaves when there’s a lot of data contention which is usually the case for tracking systems.

Original title and link: Designing a MongoDB Schema for a Monitoring System (NoSQL database©myNoSQL)

via: http://blog.pythonisito.com/2012/09/mongodb-schema-design-at-scale.html?spref=tw