[jira] Commented: (JCR-2597) JCR query execution is taking long time
[ https://issues.apache.org/jira/browse/JCR-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855526#action_12855526 ] sydaiah nallabirudu commented on JCR-2597: -- Could you please suggest , how to ask these questions on the mailing list. Do i need to register in any website? Regards Sydaiah N On Wed, Apr 14, 2010 at 8:37 AM, Alexander Klimetschek (JIRA) < > JCR query execution is taking long time > > > Key: JCR-2597 > URL: https://issues.apache.org/jira/browse/JCR-2597 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: JCR API >Affects Versions: 1.5.4 >Reporter: sydaiah nallabirudu > > Hi, > I am using the below jcr query to get the results.This query will return > approx : 226000 records. > /jcr:root/*[jcr:like(@Title, '%')]order > by @updatedDate descending|#] > This query is taking approx 8 secs to retrun the node results. > Jackrabbit application is logging the below statements, when query returns > large result sets > > [#|2010-04-08T13:37:09.039-0400|INFO|sun-appserver2.1|org.apache.jackrabbit.core.persistence.bundle.util.LRUNodeIdCache|_ThreadID=49;_ThreadName=httpSSLWorkerThread-8080-4;|num=1268/10240 > hits=0 miss=430|#] > > [#|2010-04-08T13:37:09.039-0400|INFO|sun-appserver2.1|org.apache.jackrabbit.core.persistence.bundle.util.BundleCache|_ThreadID=49;_ThreadName=httpSSLWorkerThread-8080-4;|num=647 > mem=8186k max=8192k avg=12956 hits=3140478 miss=1159522|#] > Is it meaning that jackrabbit is caching the data in memory and sorting the > data. > How can i improve the query performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2597) JCR query execution is taking long time
[ https://issues.apache.org/jira/browse/JCR-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858514#action_12858514 ] sydaiah nallabirudu commented on JCR-2597: -- Could you please suggest , how to ask these questions on the mailing list. Do i need to register in any website? Regards Sydaiah N On Wed, Apr 14, 2010 at 8:37 AM, Alexander Klimetschek (JIRA) < > JCR query execution is taking long time > > > Key: JCR-2597 > URL: https://issues.apache.org/jira/browse/JCR-2597 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: JCR API >Affects Versions: 1.5.4 >Reporter: sydaiah nallabirudu > > Hi, > I am using the below jcr query to get the results.This query will return > approx : 226000 records. > /jcr:root/*[jcr:like(@Title, '%')]order > by @updatedDate descending|#] > This query is taking approx 8 secs to retrun the node results. > Jackrabbit application is logging the below statements, when query returns > large result sets > > [#|2010-04-08T13:37:09.039-0400|INFO|sun-appserver2.1|org.apache.jackrabbit.core.persistence.bundle.util.LRUNodeIdCache|_ThreadID=49;_ThreadName=httpSSLWorkerThread-8080-4;|num=1268/10240 > hits=0 miss=430|#] > > [#|2010-04-08T13:37:09.039-0400|INFO|sun-appserver2.1|org.apache.jackrabbit.core.persistence.bundle.util.BundleCache|_ThreadID=49;_ThreadName=httpSSLWorkerThread-8080-4;|num=647 > mem=8186k max=8192k avg=12956 hits=3140478 miss=1159522|#] > Is it meaning that jackrabbit is caching the data in memory and sorting the > data. > How can i improve the query performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
