2014-04-24 6:05 GMT+09:00 John Mettraux <[email protected]>: > > On Wed, Apr 23, 2014 at 04:53:58AM -0700, Barak Merimovich wrote: >> >> As we approach the release of this new version, we encountered the issues >> Dan described above, and are looking for someone to consult us about >> resolving these issues. We have a standalone test which shows the maxed out >> CPU described previously, and will upload it shortly. We would appreciate >> any type of support you can provide.
Hello, I noticed you are using the merge-type="ignore" which is good. I guess that, at 100 iterations the concurrent iterator is not performing as you expect. Unfortunately, ruote was not designed for such "wide" c-iterations. There is an emphasis on holding to the data. Others have been bit by this in the past, with some searching, the list might yield those conversations. I know it's not the same thing, but have you thought about firing a workflow per node instead of the current approach? Also, reading diagonally, I see that you have an emphasis on "state". Wouldn't you guys be better served by a state machine library? I know you have "orchestration" in your product name, I understand you want workflow ultimately. Best regards, John -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
