Re: hotspot in System.catalog table

We saw atleast 5x improvement in Upsert performance from our streaming app just by altering table and adding UPDATE_CACHE_FREQUENCY=6 in all our tables. Overall our cluster, system.catalog table and apps looks more happy. Thanks Again! On Thu, Apr 12, 2018 at 11:37 PM, anil gupta

Re: hotspot in System.catalog table

Thanks a lot. Going to do that and see the impact. On Thu, Apr 12, 2018 at 11:33 PM, James Taylor wrote: > It’s client side, but that’ll only impact newly created tables. You’ll > need to use the ALTER TABLE command for existing tables. > > On Thu, Apr 12, 2018 at 11:30

Re: hotspot in System.catalog table

It’s client side, but that’ll only impact newly created tables. You’ll need to use the ALTER TABLE command for existing tables. On Thu, Apr 12, 2018 at 11:30 PM anil gupta wrote: > I have set phoenix.default.update.cache.frequency=6 in hbase-site.xml > via ambari(we

Re: hotspot in System.catalog table

No, that won’t make a difference. On Thu, Apr 12, 2018 at 10:51 PM anil gupta wrote: > Thanks for quick reply, James. We will look into UPDATE_CACHE_FREQUENCY > property. If we just replace PS with Statement, will it fix the > problem(AFAIK, Statement is not compiled)? >