Hi, >So are you saying, query execution will not have any impact on the cluster >activities like GET/PUTs in general ?? Why? Queries and get\put share same resources. So, they will affect each other.
>I was thinking, if we can run these queries directly on backing store, it >may not have any impact on RAM from where we always do GETs, will that work? When you use CacheStore, you have some external DB and you can run query on DB bypassing Ignite. It is clear. 1. What "backing store" do you mean when Ignite persistence is used? 2. How are you imagine query will be run on "backing store" directly? 3.Why do you think it will help you as anyway disk pressure will be increased? Moreover, disk is usually a bottleneck for PUT operations and for GET in some cases (load from disk or TTL update). On Tue, Apr 3, 2018 at 9:27 AM, Naveen <[email protected]> wrote: > Hi ANdrew > > There were cases, when I just run select * from table on SQLLINE > unknowingly, we could see queries getting slowed down and OOM errors. Our > dev machines not very high end ones. > > When we deliver this solution, production support guys can run queries to > debug any data related issues, during which they may need to join tables, > for every adhoc query we cant create indexes to speedup the query execution > right ?? > > So are you saying, query execution will not have any impact on the cluster > activities like GET/PUTs in general ?? > > I was thinking, if we can run these queries directly on backing store, it > may not have any impact on RAM from where we always do GETs, will that > work? > > Thanks > Naveen > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
