That's great! seems to eliminate a lot of the traffic. Are there any other optimizations like this you know of that we can make to reduce this any further?
We also have the issue documented in this thread: http://apache-ignite-users.70518.x6.nabble.com/Large-Heap-with-lots-of-BinaryMetaDataHolders-td34359.html I will dig out the config at some point, but is there anything obvious you can think of that would enable this sort of behaviour (e.g. retaining large binary meta data on the client node for all caches - we want to turn this off if it isn't required for the particular client). Also, another undesirable observation: 1. If client app A issues a continuous query with a remote filter and transformer to the cluster 2. When client app B starts, it seems to deserialize and log client app A's remote filter and transformer within it's own VM. Why would client app A's filter and transformer end up on client app B? Can we turn this off so client app B is isolated complete from client app A? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
