2007/1/24, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > > Have you had a look at the JcrExpressionStore ? Storing data into the > > JCR takes time. > > That's indeed where my last investigations led me. It can most > certainly be improved, but otoh, I don't see how anything it does could > take up to 10secs... probably the addition of *lots* of small things > then. > > > Nobody on the Magnolia or the OpenWFE side had the time to enhance it > > these days. > > Any ideas/directions ?
OK, storing cold into a JCR is slower than storing directly to the the disk. The obvious technique would be for the JcrExpressionStore to immediately acknowledge the expressions it receives, replying directly to the engine and storing the expressions (pieces of workflow instances) after that reply, in a separate thread. It's not as easy as it sounds : for certain workflows, the order to remove an expression might come immediately after the order to store it. I'd be really interested in helping to develop this optimization layer, it's not JCR bound, other persistences might benefit from it. We could relinquish all the JCR oriented code into JcrExpressionStore and put our ExpressionCache in front of it. BTW, does the embedded engine Magnolia uses have a CachedExpressionPool or a SimpleExpressionPool ? Best regards, :wq -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFE users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en -~----------~----~----~----~------~----~------~--~---
