Its kind of improvement. I'm not sure if it can reduce overall used memory, but probably will decrease GC pauses.
ср, 28 мар. 2018 г. в 0:09, Vyacheslav Daradur <daradu...@gmail.com>: > Aleksey, thank you, it's clear now. > > If this task is really about moving reader's information to off-heap: > do we have issues with the current implementation (e.g. at restarting) > or this task is kind of improvement? > > On Tue, Mar 27, 2018 at 11:32 PM, ALEKSEY KUZNETSOV > <alkuznetsov...@gmail.com> wrote: > > When client node performs get it stores information about itself on > server node, so-called 'reader'. > > If another node updates cache entry, server node uses 'reader' > info(because it tracks client info) to find client and update cache entry > in client's near cache. > > > > PS. obviously, there may be plenty 'reader' nodes > > > > > > Отправлено с iPhone > > > >> 27 марта 2018 г., в 22:41, Vyacheslav Daradur <daradu...@gmail.com> > написал(а): > >> > >> Dmitry, thanks, but I'm not sure that I correctly understood you. > >> > >>>> Every get operation is tracked and enlisted on server node. > >> > >> What does it mean? Is it about metrics? > >> > >>> On Tue, Mar 27, 2018 at 6:29 PM, Dmitry Pavlov <dpavlov....@gmail.com> > wrote: > >>> Hi Vyacheslav, > >>> > >>> > >>> Task is still actual. It is another question if it is a priority or > not. > >>> > >>> > >>> This is a task is about following case: a client node has near cache. > Every > >>> get operation is tracked and enlisted on server node. The server node > must > >>> trace the operation and accordingly store the results to Java Heap > Memory. > >>> Currently it is on-heap, and task is about idea to make it off-heap. > >>> > >>> > >>> Sincerely, > >>> > >>> Dmitriy Pavlov > >>> > >>> пт, 23 мар. 2018 г. в 13:13, Dmitry Pavlov <dpavlov....@gmail.com>: > >>> > >>>> Hi Igniters, > >>>> > >>>> Alexey, please step in. I did not fully understand issue description, > and > >>>> can't identify if data is still not moved from onheap. > >>>> > >>>> I suggest to consider it as outdated if we don't have any additional > info. > >>>> > >>>> Sincerely, > >>>> Dmitriy Pavlov > >>>> > >>>> чт, 22 мар. 2018 г. в 10:48, Vyacheslav Daradur <daradu...@gmail.com > >: > >>>> > >>>>> Hi, Igniters! > >>>>> > >>>>> Look like it's outdated and can be closed. > >>>>> > >>>>> Could someone comment if this ticket [1] is still valid? > >>>>> > >>>>> > >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-4662 > >>>>> > >>>>> On Wed, Jun 28, 2017 at 2:38 AM, Valentin Kulichenko > >>>>> <valentin.kuliche...@gmail.com> wrote: > >>>>>> I'm not sure this ticket is valid for 2.0. Semen, can you comment? > >>>>>> > >>>>>> -Val > >>>>>> > >>>>>> On Tue, Jun 27, 2017 at 1:14 AM, Vyacheslav Daradur < > >>>>> daradu...@gmail.com> > >>>>>> wrote: > >>>>>> > >>>>>>> Hi Igniters. > >>>>>>> > >>>>>>> I have some questions according to this task: > >>>>>>> > >>>>>>> 1. Does the method: GridCacheMapEntry#evictInternal do the > >>>>>>> eviction(on-heap > >>>>>>> -> off-heap)? > >>>>>>> 2. Is CacheOffheapEvictionManager responsible for managing the > >>>>>>> eviction(on-heap -> off-heap)? (if not, then who is?) > >>>>>>> 3. At what moment the eviction(on-heap -> off-heap) is called? > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Best Regards, Vyacheslav D. > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Best Regards, Vyacheslav D. > >> > >> > >> > >> -- > >> Best Regards, Vyacheslav D. > > > > -- > Best Regards, Vyacheslav D. >
