hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Tarnas <...@email.com>
Subject Re: Mongo vs HBase
Date Wed, 10 Aug 2011 17:09:43 GMT
Hi Laurent,

Without more details on your schema and how you are finding that number in your table it is
impossible to fully answer the question. I suspect what you are seeing is mongo's native support
for secondary indexes. If you were to add secondary indexes in HBase then retrieving that
row should be on the order of 3-30ms. If that is you main query method then you could reorganize
your table to make that long number your row key, then you would get even faster reads.


On Aug 10, 2011, at 10:02 AM, Laurent Hatier wrote:

> Hi all,
> I would like to know why MongoDB is faster than HBase to select items.
> I explain my case :
> I've inserted 4'000'000 lines into HBase and MongoDB and i must calculate
> the geolocation with the IP. I calculate a Long number with the IP and i go
> to find it into the 4'000'000 lines.
> it's take 5 ms to select the right row with Mongo instead of HBase takes 5
> seconds.
> I think that the reason is the method : cur.limit(1) with MongoDB but is
> there no function like this with HBase ?
> -- 
> Laurent HATIER
> Étudiant en 2e année du Cycle Ingénieur à l'EISTI

View raw message