Re: HBase performance

2007-10-12 Thread Jeff Hammerbacher
hmm, i'm going to have to disagree strongly with jim here on several points: 1) the paper you reference has nothing to do with column-store performance: it's all about a new, in-memory oltp system being worked on in stonebraker's lab/vertica. it's mainly about removing disk access via

Re: HBase performance

2007-10-12 Thread Jonathan Hendler
, Senior Engineer; Powerset [EMAIL PROTECTED] -Original Message- From: Jeff Hammerbacher [mailto:[EMAIL PROTECTED] Sent: Friday, October 12, 2007 9:20 AM To: hadoop-user@lucene.apache.org Subject: Re: HBase performance hmm, i'm going to have to disagree strongly with jim here

Re: HBase performance

2007-10-12 Thread Doug Cutting
Jonathan Hendler wrote: Since Vertica is also a distributed database, I think it may be interesting to the newbies like myself on the list. To keep the conversation topical - while it's true there's a major campaign of PR around Vertica, I'd be interested in hearing more about how HBase

RE: HBase performance

2007-10-12 Thread Jim Kellerman
PROTECTED] Sent: Friday, October 12, 2007 11:29 AM To: hadoop-user@lucene.apache.org Subject: Re: HBase performance Jonathan Hendler wrote: Since Vertica is also a distributed database, I think it may be interesting to the newbies like myself on the list. To keep the conversation topical

RE: HBase performance

2007-10-12 Thread Jim Kellerman
One more comment and then I'll really shut up, I promise. On re-reading the paper, you are all absolutely correct about C-Store, H-Store and Vertica. What is not in the paper and part of what he presented this week was applying column oriented stores to the TPC-H benchmark. The TPC-H OLTP

Re: HBase performance

2007-10-12 Thread Peter W.
Hi, I've had some limited experience with Oracle, SQL Server, Informix and at least one commercial in-memory database. More recently, I use mysql memory tables for fun speeding up bulk read-write operations such as: set max_heap_table_size=250*1024*1024; create table mem_proptbl (field_one

Re: HBase performance

2007-10-12 Thread Jason Watkins
- writes: a row oriented database writes the whole row regardless of whether or not values are supplied for every field or not. Space is reserved for null fields, so the number of bytes written is the same for every row. In a column oriented database, only the columns for which values

Re: HBase performance

2007-10-11 Thread Michael Bieniosek
MySQL and hbase are optimized for different operations. What are you trying to do? -Michael On 10/11/07 3:35 PM, Rafael Turk [EMAIL PROTECTED] wrote: Hi All, Does any one have comments about how Hbase will perform in a 4 node cluster compared to an equivalent MySQL configuration? Thanks,

RE: HBase performance

2007-10-11 Thread Jim Kellerman
12345678901234567890123456789012345678901234567890123456789012345 Performance always depends on the work load. However, having said that, you should read Michael Stonebraker's paper The End of an Architectural Era (It's Time for a Complete Rewrite) which was presented at the Very Large Database