You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Przemo Pakulski (JIRA)" <ji...@apache.org> on 2007/12/01 00:11:43 UTC
[jira] Updated: (JCR-1249) Improve updating of references to
version storage
[ https://issues.apache.org/jira/browse/JCR-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Przemo Pakulski updated JCR-1249:
---------------------------------
Description:
SharedItemStateManger in Update.end() methods notify virtual providers about changed node references.
For now it notifies about every changed reference separately, it results in many calls to persistence manager and makes this operation not efficient.
e.g. after importing xml including 6k of versionable nodes then saving changes using bundle MSSqlPersistenceManager, updating references in version storage takes about 27s on my env.; after proposed change doing the same in single call takes only 9 seconds.
After doing more test outside of the profiler improvement ration changed to 2:1
was:
SharedItemStateManger in Update.end() methods notify virtual providers about changed node references.
For now it notifies about every changed reference separately, it results in many calls to persistence manager and makes this operation not efficient.
e.g. after importing xml including 15k of versionable nodes then saving changes using bundle MSSqlPersistenceManager
updating references in version storage takes 27s on my env.; after proposed change doing the same in single call takes only 6 seconds.
Any objectives if i'll propose my patch here ?
Affects Version/s: 1.4
> Improve updating of references to version storage
> -------------------------------------------------
>
> Key: JCR-1249
> URL: https://issues.apache.org/jira/browse/JCR-1249
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Affects Versions: 1.3.3, 1.4
> Reporter: Przemo Pakulski
> Priority: Minor
> Fix For: 1.4
>
>
> SharedItemStateManger in Update.end() methods notify virtual providers about changed node references.
> For now it notifies about every changed reference separately, it results in many calls to persistence manager and makes this operation not efficient.
> e.g. after importing xml including 6k of versionable nodes then saving changes using bundle MSSqlPersistenceManager, updating references in version storage takes about 27s on my env.; after proposed change doing the same in single call takes only 9 seconds.
> After doing more test outside of the profiler improvement ration changed to 2:1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.