Hi Scott,
With eagetTTL=false, each time you access an entry its TTL is automatically
checked - if it is expired, the entry will be removed. It means that instead
of having a separate thread waking up and removing all of the expired
entries at the same time (and taking a chunk of CPU and IO for a
the next access
> instead of doing that in the background.
> If you add entries in large batches but access them more uniformly over time,
> it could redistribute the cost of expiring the data more evenly.
>
> Thanks,
> Stan
>
> From: scottmf
> Sent: 9 марта 2018 г. 6:
:51
To: user@ignite.apache.org
Subject: eviction performance
Hi,
I am prototyping using ignite to ingest lots of short lived events in a
system. In order to ingest the data i'm using the kafka streamer mechanism.
I'm pushing 20k events / second into the system into a partitioned off heap
cache
