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.
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
wrote:
> What I meant here "Also if I request data for ID 1 will it bring it only
> from disk or "
Hi there Amit,
(Attempt 2),
So, create a Region, you configure if the Region is to persist the data to disk
or not. There is no selective algorithm that would select which data is written
to disk and which is not. If it is configured to be persistent or eviction
overflowed, it will be written
Hi there Amit,
On Sep 7, 2020, 4:25 AM +1000, Amit Pandey , 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
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, 2
