Hi Nicolas, On 7/20/06, Nicolas Modrzyk <[EMAIL PROTECTED]> wrote: > > > > And of course, I forgot to mention the 'demanded' caching of the > > flows. I'll have a look at that too : IIRC it's very easy to > > reactivate/reimplement and that's elegant. > > That one sounds cool !
I integrated a caching mechanism inside of OpenWFE core libraries. My tests (with the standalone OpenWFE show a reduction to 25% of processes startup time). With debug fully on, I can now start a process in 3s (from the 'launch' click to the moment the workitem is stored in the worklist) (from the webclient, to the worklist, to the engine and back). It must be better in your 'embbeded OpenWFE' setting. There was a 'bug' inducing lots of unnecessary expression lookups. While debugging the initial implementation of the cache I spotted that problem and resolved it. I'm looking forward reading about your results. for the jars : http://openwfe.org/upload/ (I won't ask for a Maven upload now, I don't want Carlos to hate me) Best regards, no need for unelegant hacks, -- John Mettraux -///- http://jmettraux.openwfe.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ OpenWFE - Open source WorkFlow Engine OpenWFE-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openwfe-users
