2021-03-27 13:16:09 +03:00
|
|
|
+++
|
|
|
|
|
noatcards = True
|
|
|
|
|
isdraft = False
|
|
|
|
|
weight = 146
|
|
|
|
|
+++
|
|
|
|
|
|
2021-03-21 13:45:39 +03:00
|
|
|
# Refresh-ahead
|
|
|
|
|
|
|
|
|
|
## Introduction
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[Source: From cache to in-memory data grid](http://www.slideshare.net/tmatyashovsky/from-cache-to-in-memory-data-grid-introduction-to-hazelcast)
|
|
|
|
|
|
|
|
|
|
You can configure the cache to automatically refresh any recently accessed cache entry prior to its expiration.
|
|
|
|
|
|
|
|
|
|
Refresh-ahead can result in reduced latency vs read-through if the cache can accurately predict which items are likely to be needed in the future.
|
|
|
|
|
|
|
|
|
|
## Disadvantage(s) : refresh-ahead
|
|
|
|
|
|
|
|
|
|
- Not accurately predicting which items are likely to be needed in the future can result in reduced performance than without refresh-ahead.
|
