Which db do you use?
How many threads do you have?
Can you profile to see where is actually coming from? 

Finally, is it something that you need to do very frequently? because as you probably know in term of perfs is rarely possible to be better whatever the use case so it is important to focus on most frequent use cases only

If it is critical as it is very frequently used, please create a JIRA issue in JCR project https://jira.exoplatform.org/browse/JCR

On Thu, Oct 18, 2012 at 9:29 PM, Matt Wringe <mwringe@redhat.com> wrote:
I am looking into some performance issues, and I am seeing some
performance degradation when calling DataStorage.save() between JCR 1.14
and 1.15.

I created a simple test which loads a number of pages using the page
service and then does a datastorage.save at the end
(https://github.com/mwringe/gatein-portal/blob/b331e1868a75bbeb449c8ce589fc80fd7ac47b35/component/portal/src/test/java/org/exoplatform/portal/mop/page/TestPageImport.java).
Note: the only difference I am doing between the tests is changing the
jcr version and adding a lucene dependency for the older 1.14, all the
configuration files and such are the same.

When using JCR 1.15 versus 1.14, I am seeing about a 30% difference
below 300 pages, and then it takes over twice as long when dealing with
400+ pages. Link to spreadsheet data:
https://docs.google.com/spreadsheet/ccc?key=0AjYJ_xXGrZ-OdE12RGd5elMzTEpuLTRHdnR6YTk5V0E

Is DataStorage.save expected to be slower with JCR 1.15 (a trade-off for
some performance gain somewhere else) or is there something which needs
to be done differently when using datastorage and jcr 1.15? or maybe my
test is completely wrong :)

Thanks,

Matt Wringe
_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev