Hi Dima Umm but as i know the working of CoProcessor and Custom filter are almost same, they execute in similar fashion. *But with Coprocessor i never got such high levels of CPU usage*. Though Heap and JVM freeze are some issues with CoPro
On Mon, Jun 16, 2014 at 4:18 PM, Dima Spivak <[email protected]> wrote: > Hi Vikram, > > Maybe I'm misunderstanding your question, but isn't this expected > since coprocessors do the heavy lifting at the level of the RegionServer > whereas the client API means you hit a bottleneck as data is transferred > from each RS to your gateway? > > -Dima > > On Monday, June 16, 2014, Vikram Singh Chandel < > [email protected]> > 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. > > > -- *Regards* *VIKRAM SINGH CHANDEL* Please do not print this email unless it is absolutely necessary,Reduce. Reuse. Recycle. Save our planet.
