On Fri, Jun 18, 2010 at 01:39:47PM -0700, I. E. Smith-Heisters wrote: > > we're trying to migrate from FsStorage to the new ruote-couch 2.1.10 > with CouchDB 0.11.0. I'm noticing that timeouts and sleeps used in our > test code have to be significantly higher in order to allow the worker > thread to reach the expected state. Where once we might do > > -- > wfid = engine.launch pdef, *args > sleep 0.2 > engine.process(wfid) # => Ruote::ProcessStatus > -- > > ... we now need to wait for 2 or 3 seconds. Is this expected? Is there > some way around this? Or are we doing something terribly wrong?
Hello, no, no you are not doing anything wrong. http://ruote.rubyforge.org/configuration.html#storage ruote-couch is simply the slowest storage around. I'm using it here, but the projects imply 'classical' business processes with most of the step performed by humans, so this 'slowness' doesn't appear. Of course I'm trying to improve this situation, but, well FsStorage reads local files, while CouchStorage grabs information over HTTP... Help is welcome. Best regards, -- John Mettraux - http://jmettraux.wordpress.com -- 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
