[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704147#action_12704147
]
Erik Holstad commented on HBASE-1249:
-------------------------------------
So was a little bit confused when it came to the number of compares for the old
version yesterday, somehow I thought that the deletes structure was a hashset,
but it is a sorted set.
So the number of compares for getting becomes k*l+ l*log(m) and for the new
k+l+m, which if you just wanna put some totally unreasonable test numbers in
there just to get a feeling, k=l=m=8 turns out to be
8*8 + 8*3 = 64+24 = 88 vs 8+8+8 = 24.
For the new code, like said earlier the most complex part is the merging of the
lists and specially the merge of the deletes. On the other hand it is very easy
to write unit test for this to test it in isolation, which has also been done.
> Rearchitecting of server, client, API, key format, etc for 0.20
> ---------------------------------------------------------------
>
> Key: HBASE-1249
> URL: https://issues.apache.org/jira/browse/HBASE-1249
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Jonathan Gray
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HBASE-1249-Example-v1.pdf, HBASE-1249-Example-v2.pdf,
> HBASE-1249-GetQuery-v1.pdf, HBASE-1249-GetQuery-v2.pdf,
> HBASE-1249-GetQuery-v3.pdf, HBASE-1249-GetQuery-v4.pdf,
> HBASE-1249-StoreFile-v1.pdf, HBASE-1249-StoreFile-v4.pdf
>
>
> To discuss all the new and potential issues coming out of the change in key
> format (HBASE-1234): zero-copy reads, client binary protocol, update of API
> (HBASE-880), server optimizations, etc...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
