Re: Ignite.Net Server & client node

2019-11-12 Thread Sudhir Patil
Thanks Pavel. I will look into those. Regards Sudhir On Wednesday, November 13, 2019, Pavel Tupitsyn wrote: > Sure, you can query multiple items as well in various ways - see > ICache.Query method [1] > ICache is also IEnumerable, so you can iterate over entire contents, and > even call ToList/

Re: Ignite.Net Server & client node

2019-11-12 Thread Pavel Tupitsyn
Sure, you can query multiple items as well in various ways - see ICache.Query method [1] ICache is also IEnumerable, so you can iterate over entire contents, and even call ToList/ToArray on it for smaller caches. [1] https://apacheignite-net.readme.io/docs/cache-queries On Tue, Nov 12, 2019 at 7:

Re: Ignite.Net Server & client node

2019-11-12 Thread Sudhir Patil
Thanks Pavel. I want both - both whole list and individual items within that list to be queried from cache. Hence was asking on that side. Regards, Sudhir On Monday, November 11, 2019, Pavel Tupitsyn wrote: > As I understood, you store the whole list of 1 employees as a single > object: >

Re: Ignite.Net Server & client node

2019-11-11 Thread Pavel Tupitsyn
As I understood, you store the whole list of 1 employees as a single object: cache[key] = GetAllEmployees(); Instead, try storing every employee object separately: foreach (var employee in GetAllEmployees()) cache.Put(employee.Id, employee) This way you can retrieve individual employees q

Re: Ignite.Net Server & client node

2019-11-11 Thread Sudhir Patil
Hi Pavel, Scenario is - i am caching list of let's say 1 employee poco class objects with name 'employeeCache'. Now, from this cache, I want to get employee object with id 1500. 1) For this what is fastest & efficient way ? Simple one is get full cache data i.e. 'employeeCache' object and then

Re: Ignite.Net Server & client node

2019-11-11 Thread Sudhir Patil
Iliya, Thanks. Regards, Sudhir On Monday, November 11, 2019, Ilya Kasnacheev wrote: > Hello! > > Oh! In this case there's not much to do, except maybe use something like > EhCache for local opportunistic caching. > > Regards, > -- > Ilya Kasnacheev > > > пн, 11 нояб. 2019 г. в 10:43, Pavel Tup

Re: Ignite.Net Server & client node

2019-11-11 Thread Ilya Kasnacheev
Hello! Oh! In this case there's not much to do, except maybe use something like EhCache for local opportunistic caching. Regards, -- Ilya Kasnacheev пн, 11 нояб. 2019 г. в 10:43, Pavel Tupitsyn : > Ilya, I think thin client was mentioned in the first post - near cache > does not do much for t

Re: Ignite.Net Server & client node

2019-11-10 Thread Pavel Tupitsyn
Ilya, I think thin client was mentioned in the first post - near cache does not do much for thin clients On Mon, Nov 11, 2019 at 10:23 AM Ilya Kasnacheev wrote: > Hello! > > You can actually configure near cache to store these records alongside > your client node: > > https://apacheignite-net.re

Re: Ignite.Net Server & client node

2019-11-10 Thread Ilya Kasnacheev
Hello! You can actually configure near cache to store these records alongside your client node: https://apacheignite-net.readme.io/docs/near-caches Regards, -- Ilya Kasnacheev пт, 8 нояб. 2019 г. в 20:37, Sudhir Patil : > Hi All, > > In ignite.net server node stores cache data and a thin cli

Re: Ignite.Net Server & client node

2019-11-10 Thread Pavel Tupitsyn
Sudhir, I'm not sure I fully understand the question. You certainly don't have to fetch 1 million objects when you need only one. - If you have a key, use ICache.Get, it is the fastest API to get a single value. - If you don't have a key, but rather want to search for something (e.g. find a Person

Ignite.Net Server & client node

2019-11-09 Thread Sudhir Patil
Hi Pavel, Thank you for details. Is there a way to improve performance in such subsequent requests ? Scenario is - lets say cache is storing data e.g. 1 million list of custom poco class objects. Now it needs only one specific poco object out of it. Here this operation would fetch full cache i.e.

Re: Ignite.Net Server & client node

2019-11-08 Thread Pavel Tupitsyn
Hi, Every request is communicated to the server, there is no "local cache" or anything like that. On Fri, Nov 8, 2019 at 8:37 PM Sudhir Patil wrote: > Hi All, > > In ignite.net server node stores cache data and a thin client > communicates with server to get cache data. > > In such situations,

Ignite.Net Server & client node

2019-11-08 Thread Sudhir Patil
Hi All, In ignite.net server node stores cache data and a thin client communicates with server to get cache data. In such situations, post 1 request of cache data by thin client, does all further requests still communicate with server or it stores that cache data on thin client and server from th