Hi, After having migrated a project to use the embedded, we notice pretty poor apparent performance. Please note that I am not accusing openwfe (not yet anyway ;) but it *seems* that every operation takes about 10 seconds or more. "Operation" in this case would mean launching/proceeding but also storing the workitem, getting the list of wi's back from the engine, displaying them and any further process that the application does with or without the workitems behind the scenes. I am under the *impression* that it's not a performance issue, but that each task done by openwfe is done through a scheduler and that it could perfectly handle doing more things more often. (launching usually takes slightly longer, but proceeding usually is about 10 secs)
Now, looking at the code, I'm a bit confused, because I see that the Scheduler is nudged 4 times a second, which sounds reasonable. But then I see - but I might need to check again - that it's only actually executing one single "pending job" per run. Which means a maximum of 4 jobs per second, which alreads sounds less agreable. Now I'm not sure what's in such a job: if launching or proceeding are atomic "jobs" then we're fine and my problem is elsewhere; if not, then maybe that's not where my problem resides at all at the moment, but maybe it is. I'm obviously looking at some profiler data, but all I see for now, is confirmation that the actual processing doesn't take that long, but that somehow the system is just busy doing nothing for a while. I'll appreciate any tip or idea ! Cheers, greg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
