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
Wednesday, 10 November 2010
‹ Back

Notes on data warehouse appliance prices

About:
,

Curt Monash:

Reasons people criticize per-terabyte data warehouse appliance price metrics include:

  • Price-per-terabyte metrics ignore issues of throughput, latency, workload, and so on.
  • Price-per-terabyte metrics ignore quality of storage medium (slow disks, fast disks, Flash, etc.)
  • Price-per-terabyte metrics can be radically affected by changes in disk size.

Not a specialist, but I don’t think the price-per-terabyte includes operational costs either.

Original title and link: Notes on data warehouse appliance prices (NoSQL databases © myNoSQL)

via: http://www.dbms2.com/2010/10/15/pricing-of-data-warehouse-appliances/