jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashank Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3734) Slow local cache built-up time
Date Thu, 20 Feb 2014 11:12:19 GMT
Shashank Gupta created JCR-3734:

             Summary: Slow local cache built-up time
                 Key: JCR-3734
                 URL: https://issues.apache.org/jira/browse/JCR-3734
             Project: Jackrabbit Content Repository
          Issue Type: Sub-task
            Reporter: Shashank Gupta

urrently with the S3 connector, it appears that the startup will attempt to scan the local
datastore on local disk and slow down the startup process. Attached are the thread dumps,
profiling results and logs for further investigation. It will be great if the startup can
avoid such a scan or this can be optimised further.

Customer's  business impact -

" It's going to be a scalability issue as the cache grows. Currently we only have 64GB or
less, which takes 8+ minutes, if we double or quadruple the cache, application startup is
going to be far too slow for us. We might be able to take advantage of SSD attached disk rather
than HDD attached disk, but we need to evaluate this option further and we want a better fix
than simply throwing faster storage at it.

Ideally we want repository to come online as fast as possible and complete any cache size
counting activities in the background, or have repository retain a memory of it's cache status
from when it was last running so that at startup it picks up it's state and doesn't need to
scan the whole cache."

This message was sent by Atlassian JIRA

View raw message