Re: Issue with large number of Continuous Queries

2020-02-11 Thread Denis Magda
Hello, How do you decide about a number of continuous queries to be started? I see on one of your pictures that a query is started per key. Usually, a single query per cache per client should be enough as long as the filter allows to exclude records of no interest for a client. Probably, you can p

Re: Issue with large number of Continuous Queries

2020-02-11 Thread Andrei Aleksandrov
Hi, Please read some comments below: 1)You said: *Scenario*: There are 1000 items in the myCache and client-1 is pushing 3 updates per second on every item. Lets say both client-2 and client-3 have 1000 different continuous queries open to listen to every update. Continues query can handle all

Issue with large number of Continuous Queries

2020-02-11 Thread zork
*Topology*: Server-1 --> Cache myCache, holds continuously updating data like market data(prices, status, tradetime etc) for instruments. InstrumentId is the key for this cache. Server-1 running with following jvm params: -Xms1g,-Xmx6g Client-1 --> Pushing continuous updates on

Issue with large number of Continuous Queries

2020-02-11 Thread zork
*Topology*: Server-1 --> Cache myCache, holds continuously updating data like market data(prices, status, tradetime etc) for instruments. InstrumentId is the key for this cache. Server-1 running with following jvm params: -Xms1g,-Xmx6g Client-1 --> Pushing continuous updates on

Issue with large number of Continuous Queries

2020-02-10 Thread Dorah
*Topology*: Server-1 --> Cache myCache, holds continuously updating data like market data(prices, status, tradetime etc) for instruments. InstrumentId is the key for this cache. Server-1 running with following jvm params: -Xms1g,-Xmx6g Client-1 --> Pushing continuous updates on