You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Shashank Gupta (JIRA)" <ji...@apache.org> on 2014/10/13 16:24:33 UTC
[jira] [Commented] (JCR-3817) [jackrabbit-aws-ext] Performance of
normal operation degrades while running GC
[ https://issues.apache.org/jira/browse/JCR-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169333#comment-14169333 ]
Shashank Gupta commented on JCR-3817:
-------------------------------------
* The idea is to update the lastModified asynchronously.
* It keeps a in-memory map which holds all in-progress async touch.
* Successful updation of lastModified will remove the entry from map.
* Async touch will not work in shared datastore mode and hence it is kept configurable and by default it is disabled.
*
> [jackrabbit-aws-ext] Performance of normal operation degrades while running GC
> ------------------------------------------------------------------------------
>
> Key: JCR-3817
> URL: https://issues.apache.org/jira/browse/JCR-3817
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-data
> Affects Versions: 2.9
> Reporter: Shashank Gupta
> Fix For: 2.9.1
>
>
> It is because when GC is running lastModified of each record is updated in S3 which affects the performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)