How does the Caribbean forest evict on a map, in terms of its streaming model?

Question

I understand that <min-eviction-check-millis>in the walnut configuration , it determines the minimum time, in milliseconds, that must elapse before checking whether a section of this card is allowed or not. Therefore, during each configured interval, eviction will be performed on the card in accordance with the configured eviction policy. I have the following questions related to this area.

Q1. Is an eviction operation in progress?

Q2. Will the eviction operation block the entire partition that it is working on?

Q3. Should I expect any performance improvement if I follow the standard values ​​of 100 ms (which I consider very small).

Q4. How often the eviction operation will be performed in the following scenario.

<map name="employees">
    <in-memory-format>BINARY</in-memory-format>
    <backup-count>1</backup-count>
    <max-idle-seconds>1800</max-idle-seconds>
    <eviction-policy>NONE</eviction-policy>
    <time-to-live-seconds>0</time-to-live-seconds>
    <min-eviction-check-millis>1000</min-eviction-check-millis>
    <max-size>0</max-size>
    <eviction-percentage>0</eviction-percentage>
    <merge-policy>com.hazelcast.map.merge.PutIfAbsentMapMergePolicy</merge-policy>

</map>

Please note that although the eviction policy and percentage setting are not defined, the maximum wait time is set to 1800 seconds.

Answering the above questions will help me make an informed decision about the values ​​that will be used for these configurations in a large-scale deployment.

Answer 1

min-eviction-check-millis - - . min-eviction-check-millis = 0; . min-eviction-check-millis = 1000; , 1 .

, , 0. .

Q1. ?

. (map.put, map.get, map.remove ..).

Q2. , ?

. , .

Q3. - , 100 ( ).

, , . , ; .

Q4. .

. , . min-eviction-check-millis max-size .

max-idle-seconds ( ttl) - . . , . ; , . .