Amit,
You can find high level details at:
https://geode.apache.org/docs/guide/112/developing/storing_data_on_disk/chapter_overview.html
Geode keeps the Key always in memory. Geode creates different Region-Entries
(Key-Value pair) based on the region configuration and how/where data is
stored.
When application tries to retrieve data for a given key, it knows where to look
for it in the disk and loads it to the memory (only that value).
There are certain operation like querying, where getting the data into memory
is avoided, as it does region/index scan.
-Anil.
On 9/7/20, 11:57 PM, "Amit Pandey" <amit.pandey2...@gmail.com> wrote:
I agree its kind of academic but any answers will be appreciated, I just
wanted to understand the performance characteristics when using disk
persistence
On Sun, Sep 6, 2020 at 11:54 PM Amit Pandey <amit.pandey2...@gmail.com>
wrote:
> What I meant here "Also if I request data for ID 1 will it bring it only
> from disk or " was that if I request a tuple which is not in memory and is
> in disk,
> 1) How does Geode know its in DISK
> 2) Does it bring only that tuple (value) to Memory or brings the whole
> page
>
> Regards
>
>
> On Sun, Sep 6, 2020 at 11:36 PM Amit Pandey <amit.pandey2...@gmail.com>
> wrote:
>
>> Hi Geode Devs,
>>
>> How does Geode handle data on disk ? How does Geode mark that some data
>> of a region is in disk , is it basically what we call as the Tombstone
>> approach ? Also if I request data for ID 1 will it bring it only from
disk
>> or
>>
>> Secondly, how does Geode handle updates of data on disk ? SO does it
>> discard the data on disk when it brings a tuple in memory and writes a
new
>> file to disk ?
>>
>> Regards
>>
>>
