hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Why Custom Filters are more resource exhaustive then normal single column value filter
Date Mon, 16 Jun 2014 13:22:23 GMT
Can you format the table for better reading ?
You can put picture on third party website and post link here. 

Does your custom filter maintain state ?

What hbase version are you using ?

Have you checked region server logs during the 15 minutes ?

Cheers

On Jun 16, 2014, at 3:25 AM, Vikram Singh Chandel <vikramsinghchandel@gmail.com> wrote:

> Hi
> I was working on way to find a substitute for coprocessor(because of
> various issue with them)
> so tried Custom Filters and found that the custom filter are much more
> resource exhaustive (CPU) then coprocessor having single column value
> filter.
> 
> *Query: Get List of Publications for UDANDA (CF:Attributes Col:Country) -
> Result: 509 Records. *
> 
> *Heap 3 Gb *
> 
> 
> With Custom Filter
> No of Scan Req
> Max Heap(Mb)
> Max CPU(%)
> 
> 
> 
> 1
> 86.74
> 7.7
> 5
> 412
> 63.37
> 10
> 926
> 99
> *With Single Column Value Filter*
> No of Scan Req
> Max Heap
> Max CPU
> 
> 
> 
> 10
> 453.66
> 17.7
> Query ran for 15 minutes didn't get results. Terminated execution
> 
> 
> 
> *Can anyone shed some light on this.*
> -- 
> 
> *Regards*
> 
> *VIKRAM SINGH CHANDEL*
> 
> Please do not print this email unless it is absolutely necessary,Reduce.
> Reuse. Recycle. Save our planet.

Mime
View raw message