> > Hello Marco, > > instead of "return false", you could do > > @context.storage.put_msg(msg['action'], msg) > return true >
Hi John, now the worker does its job and only for the specified participants, great :-) > OK, I've been thinking about your situation and tried a small experiment: > > https://github.com/jmettraux/ruote-redis/tree/experiment_pipe_pop > > It's pipelining 28 rpops. I found (via > https://github.com/jmettraux/ruote-redis/blob/experiment_pipe_pop/test/bm/loaded.rb > ) that it performs faster than the current (mea culpa) single pop. > > I haven't tried with multiple workers. > > Would you have time to test that (in your staging env somehow)? > great, I gave it a try, our test-suite runs green. and as far as I can see, it works correctly with multiple workers too. I took a manual benchmark with 30 workitems running thru a workflow: 2 workers - 1:45 ruote-redis 2 workers - 1:37 ruote-redis-experimental But this is not very representative as we have some time-consuming jobs going on, I think the pure ruote-speedup must be far more. Would be cool, to have this optimization in master soon. Thanks a lot! Marco > -- > John Mettraux - http://lambda.io/jmettraux > > -- > 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 "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
