jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Stocker (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3004) Check if a DAV-Request has a Label in the header, before checking if it's version-controlled
Date Sun, 26 Jun 2011 06:49:47 GMT
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
         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

        

Mime
View raw message