hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Rawson <ryano...@gmail.com>
Subject Re: Does HBase need caching layer if it served webpage
Date Fri, 15 Oct 2010 03:07:24 GMT
HBase has excellent performance, and is suitable for serving webpages.
 We do this at Stumbleupon.  We can get responses out of hbase in
millisecond oriented intervals, and generally things are great.

You will need to adjust all these expectations for your environment -
we run i7 based hardware in our own datacenter.  You can't really get
much better perf for your bucks, and ec2 has substantially lower


On Thu, Oct 14, 2010 at 5:32 PM, Sean Bigdatafun
<sean.bigdatafun@gmail.com> wrote:
> Google mentioned that it uses Bigtable to serve map-tiles, which basically
> means it uses Bigtable to serve huge amount of data online, but it does not
> mention any caching layer. But we all know HBase's random read performance
> sucks (this is true for Bigtable as well, see their paper: even you increase
> the number of servers for 500 times, the random read throughput just
> increases 3-4 times).
> I am wonder how are people handle it, any experience to share?
> Also, can someone talk about what kind of caching layer can be added if
> anyone practieces that?
> Sean

View raw message