Comments on: Introduction to Aster Data and nCluster http://www.dbms2.com/2008/09/02/introduction-to-aster-data-and-ncluster/ Choices in data management and analysis Thu, 09 Feb 2012 16:57:09 +0000 hourly 1 http://wordpress.org/?v=3.0.3 By: Confluence: Client: Telefonica I+D http://www.dbms2.com/2008/09/02/introduction-to-aster-data-and-ncluster/#comment-158366 Confluence: Client: Telefonica I+D Fri, 05 Feb 2010 15:23:00 +0000 http://www.dbms2.com/?p=514#comment-158366 <strong>personalization server old code and architecture review...</strong> (form SVN) (see part list at... personalization server old code and architecture review…

(form SVN) (see part list at…

]]> By: Web analytics — clickstream and network event data | DBMS2 -- DataBase Management System Services http://www.dbms2.com/2008/09/02/introduction-to-aster-data-and-ncluster/#comment-97766 Web analytics — clickstream and network event data | DBMS2 -- DataBase Management System Services Mon, 22 Sep 2008 10:11:09 +0000 http://www.dbms2.com/?p=514#comment-97766 [...] Data’s largest disclosed database, by almost two orders of magnitude, is at [...] [...] Data’s largest disclosed database, by almost two orders of magnitude, is at [...]

]]> By: Roger http://www.dbms2.com/2008/09/02/introduction-to-aster-data-and-ncluster/#comment-96642 Roger Wed, 03 Sep 2008 21:53:26 +0000 http://www.dbms2.com/?p=514#comment-96642 What their pricing model? Per terabyte? And how much it costs? What their pricing model? Per terabyte? And how much it costs?

]]> By: Steve Wooledge http://www.dbms2.com/2008/09/02/introduction-to-aster-data-and-ncluster/#comment-96620 Steve Wooledge Wed, 03 Sep 2008 18:21:42 +0000 http://www.dbms2.com/?p=514#comment-96620 Hi Curt, Thanks for the post. Just a couple points for clarification: [1] At MySpace, every piece of data has 2 copies on distinct nodes. More specifically, at MySpace, as well as our other customers, they use RAID 0 on the Aster Worker nodes and RAID 10 on the Aster Queen nodes. [more on our 3-tiered architecture here: (http://www.asterdata.com/product/architecture.html)] Our recommendation is to always use RAID 0 on the workers, because it gives you better performance when a disk fails: with RAID10, if a disk fails, the node stays available, but the performance of that node drops by 50% (and, thus, the performance of the cluster). Because we have full replication and transparent failover, in Aster nCluster if a disk fails, the entire node goes down, but nCluster’s performance only drops by 1/n th (where n is the number of nodes). [2] re: "parallel query" - The local GROUP BYs is an example; our query optimization algorithms cover the relational algebra and not just 1 case. Hi Curt,

Thanks for the post. Just a couple points for clarification:

[1] At MySpace, every piece of data has 2 copies on distinct nodes. More specifically, at MySpace, as well as our other customers, they use RAID 0 on the Aster Worker nodes and RAID 10 on the Aster Queen nodes. [more on our 3-tiered architecture here: (http://www.asterdata.com/product/architecture.html) Our recommendation is to always use RAID 0 on the workers, because it gives you better performance when a disk fails: with RAID10, if a disk fails, the node stays available, but the performance of that node drops by 50% (and, thus, the performance of the cluster). Because we have full replication and transparent failover, in Aster nCluster if a disk fails, the entire node goes down, but nCluster’s performance only drops by 1/n th (where n is the number of nodes).

[2] re: “parallel query” – The local GROUP BYs is an example; our query optimization algorithms cover the relational algebra and not just 1 case.

]]>