Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 15 May 2013 06:21:16 +0000 (UTC)
From: "Shashank Gupta (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12639251.1364358663424.321994.1368598876541@arcas>
In-Reply-To: <JIRA.12639251.1364358663424@arcas>
References: <JIRA.12639251.1364358663424@arcas>
Subject: [jira] [Comment Edited] (JCR-3547) Datastore GC doesn't reset
 updateModifiedDateOnAccess on datastore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-3547?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D136580=
96#comment-13658096 ]=20

Shashank Gupta edited comment on JCR-3547 at 5/15/13 6:21 AM:
--------------------------------------------------------------

[~tmueller] were you able to apply patch. It would be performance improveme=
nt from s3 ds point of view . [1]

https://issues.apache.org/jira/browse/JCR-3547?focusedCommentId=3D13614937&=
page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#com=
ment-13614937

               =20
      was (Author: shgupta):
    [~tmueller] a gentle reminder. It would be performance improvement from=
 s3 ds point of view . [1]

https://issues.apache.org/jira/browse/JCR-3547?focusedCommentId=3D13614937&=
page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#com=
ment-13614937

                 =20
> Datastore GC doesn't reset updateModifiedDateOnAccess on datastore
> ------------------------------------------------------------------
>
>                 Key: JCR-3547
>                 URL: https://issues.apache.org/jira/browse/JCR-3547
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.4, 2.5
>            Reporter: Shashank Gupta
>         Attachments: GarbageCollector.java.patch, GC_prevent_concurrent_r=
un_app2.patch, GC_prevent_concurrent_run_final.patch, GC_prevent_concurrnet=
_run_app1.patch
>
>
> In mark phase, GC updates store.updateModifiedDateOnAccess with current t=
ime, so that datastore updates record=E2=80=99s lastModified timestamp upon=
 subsequent read/scan.
>  But  GC doesn't reset it to 0. So even after GC completes, datastore wil=
l continue updating lastModified timestamp on read invocations and it will =
have performance impact.=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira