Hi Wojciech, HBase can easily be used as a versioned key/value store. I'd say that's one of the easiest ways to use it.
To help you get more throughput, you'll have to provide more details. What version are you running, what kind of hardware / configuration, and what does your client look like that is doing the writes? Each KV is a distinct Put operation? Normally people get high throughput by batching many Puts at once. During your writes, what do you see in the RegionServer logs? Are things calm or a lot of things happening? You could also be dealing with some cold start issues if you don't have enough regions in your table or if your writes are not distributed across the keyspace. JG > -----Original Message----- > From: Wojciech Langiewicz [mailto:[email protected]] > Sent: Wednesday, November 03, 2010 4:19 AM > To: [email protected] > Subject: HBase as a versioned key/value store > > Hello, > I would like to know if any of is are using HBase as a versioned > key/value store. What I mean by versioned is keys map to multiple > values > with timestamp. > > So the whole table would have many rows and only one column family with > one column. > > I'm trying to work out what performance could I get from this design, > because right now I can only get about 1500 - 2000 requests per second > on 4 medium servers, and I'd like to get about 10x more. I know that > it's not optimal use for HBase, but if only it was 10x faster I would't > have to use any other system for this. > > Thanks in advance for any ideas. > > -- > Wojciech Langiewicz
