[
https://issues.apache.org/jira/browse/OAK-9398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Smiljanic updated OAK-9398:
------------------------------------
Description:
[CachingArchiveManager|https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.38.0/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/persistentcache/CachingArchiveManager.java]
is retrieving segment from PersistentCache if it is available there, and if it
is not, segment is retrieved from the underlying storage. On cache miss, after
segment is fetched from the storage, it is also loaded in the cache.
It would be good to provide the same option for segment write operation: after
segment is persisted to the remote storage, write the same segment to the
cache. It is useful if segment will be needed soon after, and by having it
already in the cache it can save time because segment does not need to be
loaded from the remote storage (i.e. Azure of AWS).
was:
[CachingArchiveManager|https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.38.0/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/persistentcache/CachingArchiveManager.java]
is retrieving segment from PersistentCache if it is available there, and if it
is not, segment is retrieved from the underlying storage. On cache miss, after
segment is fetched from storage, it is also loaded in the cache.
It would be good to provide the same option for segment write operation: after
segment is persisted to the storage, after operation finishes write the same
segment to the cache. It is useful if segment will be needed soon after, and by
having it already in the cache it can save time because segment does not need
to be loaded from the remote storage (i.e. Azure of AWS).
> After segment is persisted provide possibility to save it in 3rd level cache
> ----------------------------------------------------------------------------
>
> Key: OAK-9398
> URL: https://issues.apache.org/jira/browse/OAK-9398
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Miroslav Smiljanic
> Priority: Major
>
> [CachingArchiveManager|https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.38.0/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/spi/persistence/persistentcache/CachingArchiveManager.java]
> is retrieving segment from PersistentCache if it is available there, and if
> it is not, segment is retrieved from the underlying storage. On cache miss,
> after segment is fetched from the storage, it is also loaded in the cache.
> It would be good to provide the same option for segment write operation:
> after segment is persisted to the remote storage, write the same segment to
> the cache. It is useful if segment will be needed soon after, and by having
> it already in the cache it can save time because segment does not need to be
> loaded from the remote storage (i.e. Azure of AWS).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
