You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2016/11/04 14:30:58 UTC
[jira] [Comment Edited] (OAK-4837) Improved caching for DataStore
[ https://issues.apache.org/jira/browse/OAK-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575014#comment-15575014 ]
Thomas Mueller edited comment on OAK-4837 at 11/4/16 2:30 PM:
--------------------------------------------------------------
SmallFileWriteTest/SmallFileReadTest for different file sizes (50 KB, 250 KB, 1 MB, 5 MB) with different implementation:
* FileDataStore
* JR2 S3 (Using JR2 CachingDataStore)
* S3 (Using the new AbstractSharedCachingDataStore)
There is a small improvement in the writes ~13-15% but tapers of as File size increases.
!FileWriteBenchmark.png|width=900,height=400!
The read performance is approximately same for all the 3 DataStores using default caching parameters.
!FileReadBenchmark.png|width=900,height=400!
was (Author: amitjain):
SmallFileWriteTest/SmallFileReadTest for different file sizes (50 KB, 250 KB, 1 MB, 5 MB) with different implementation:
* FileDataStore
* JR2 S3 (Using JR2 CachingDataStore)
* S3 (Using the new AbstractSharedCachingDataStore)
There is a small improvement in the writes ~13-15% but tapers of as File size increases.
!FileWriteBenchmark.png|width=900,height=1200!
The read performance is approximately same for all the 3 DataStores using default caching parameters.
!FileReadBenchmark.png|width=900,height=1200!
> Improved caching for DataStore
> ------------------------------
>
> Key: OAK-4837
> URL: https://issues.apache.org/jira/browse/OAK-4837
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
> Reporter: Amit Jain
> Assignee: Amit Jain
> Labels: performance
> Fix For: 1.6
>
> Attachments: FileReadBenchmark.png, FileReadBenchmark_0Cache.png, FileWriteBenchmark.png
>
>
> The current CachingDataStore implementation used with S3DataStore has certain problems:
> * Lack of stats to show hit rate/miss rates for files being requested for downloads
> * Lack of stats for async uploads
> * CachingDataStore starts proactively downloading files in the background when a call to {{getRecord}} is made.
> * Async upload functionality leaks into Backend implementations, LocalCache classes.
> * The call to {{DataStore#getRecord()}} which makes multiple calls to backends which is problematic for S3 (i.e. when not being served bu cache)
> * There is some functionality which is not used with Oak like length cache, sync/async touch etc. which can be removed and code simplified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)