You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Christian Stocker (JIRA)" <ji...@apache.org> on 2011/07/21 10:32:58 UTC
[jira] [Commented] (JCR-3004) Check if a DAV-Request has a Label in
the header, before checking if it's version-controlled
[ https://issues.apache.org/jira/browse/JCR-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068859#comment-13068859 ]
Christian Stocker commented on JCR-3004:
----------------------------------------
Guten Tag,
Ich bin bis am 23. Juli 2011 abwesend und werde meine Emails nicht lesen.
Bitte senden Sie in dringenden Fällen eine E-Mail an contact@liip.ch.
Besten Dank für Ihr Verständnis.
Christian Stocker
***
Hi
I'm off until 23 July and do not read my emails.
In urgent cases, please send an email to contact@liip.ch
Best Wishes
Christian Stocker
--
Liip AG // Feldstrasse 133 // CH-8004 Zurich
Tel +41 43 500 39 81 // Mobile +41 76 561 88 60
www.liip.ch // blog.liip.ch // GnuPG 0x0748D5FE
> Check if a DAV-Request has a Label in the header, before checking if it's version-controlled
> --------------------------------------------------------------------------------------------
>
> Key: JCR-3004
> URL: https://issues.apache.org/jira/browse/JCR-3004
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-server
> Affects Versions: 2.2.7, 2.3.0
> Reporter: Christian Stocker
> Assignee: angela
> Fix For: 2.3.0
>
> Attachments: patch_commit_85c91801358a.patch
>
>
> When looking at our MySQL logs, I realized that jackrabbit on each DAV Request calls the VERSION table every time I get a new node (which is not cached yet), even if I only do a simple getNode.
> As a versioning table can get pretty large, this may have a performance impact.
> I found out, that DavResourceFactoryImpl checks, if a node is versioned to decide, if we have to check for the Label header to later check out another version for the GET request. I re-ordered those checks now so that it first checks, if there's an http Label-header and only then checks, if the node is versioned. The check for a Label header should be much faster than checking a DB, if it's versioned (and scale much better, too)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira