Hi, We are building a workflow system for a process that queries some other sytems (DB's and via http) and use ruote-redis for storage. When I start a single workflow process, the whole process is finished within 10 seconds. But when starting more processes (15) at the same time, the processing time increases to 30 seconds. When we start even more, we see that eventually all the workflow processes get stuck.
To make sure that the database or http calls are not the problem, I removed all these calls, and replaced the code in the :on_workitem calls with a dummy code that adds a dummy value to the workitem and does a reply. That speeds up the workflow process very little to 20 seconds, while a single workflow at a time with db and http calls is finished in 10 seconds. This seems similar to the problem described in this https://groups.google.com/forum/#!topic/openwferu-users/0shOiU7ab8M post. We didn't manage to speed up the process with more instances of the workflow application (we use AMQP to send the messages, so we can easily add more instances), or by running multiple workers of engines within a single instance of the workflow application. Switching to the FS Storage didn't solve the problem either. So far, we didn't have any luck solving this problem. Do you have any ideas what the best approach would be to pinpoint this problem? Any ideas where to look? We use ruby-2.0.0-p195, ruote (2.3.0.2), ruote-redis (2.3.0). Thanks a lot, Jarra -- -- 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/groups/opt_out.
