[ 
https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083877#comment-16083877
 ] 

ramkrishna.s.vasudevan edited comment on HBASE-17738 at 7/14/17 3:38 AM:
-------------------------------------------------------------------------

bq.The math in calculating the number of BBs per thread seems some thing wrong.
I agree. Thanks for the catch. The change was done in my other box and was not 
put up in my other place. Good catch.
bq.ets make the Callable return a BB[] so that u can avoid the start and end 
index math and changing a shared variable from diff threads.
Ok. I will take up ur suggestion that we discussed internally.


was (Author: ram_krish):
bq.The math in calculating the number of BBs per thread seems some thing wrong.
I agree. Thanks for the catch. The change was done in my other box and was not 
put up in my other place. Good catch.
bq.ets make the Callable return a BB[] so that u can avoid the start and end 
index math and changing a shared variable from diff threads.
Ok. I will take up ur suggestion and the patch that you gave me here.

> BucketCache startup is slow
> ---------------------------
>
>                 Key: HBASE-17738
>                 URL: https://issues.apache.org/jira/browse/HBASE-17738
>             Project: HBase
>          Issue Type: Sub-task
>          Components: BucketCache
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17738_2.patch, HBASE-17738_2.patch, 
> HBASE-17738_3.patch, HBASE-17738_4.patch, HBASE-17738_5_withoutUnsafe.patch, 
> HBASE-17738_6_withoutUnsafe.patch, HBASE-17738.patch
>
>
> If you set bucketcache size at 64G say and then start hbase, it takes a long 
> time. Can we do the allocations in parallel and not inline with the server 
> startup?
> Related, prefetching on a bucketcache is slow. Speed it up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to