Hi, I'm part of the IFAD development team and we are currently using Ruote in some of our projects.
After using it with CouchDB, Redis and PostgreSQL we realized that the ruote worker is always consuming between 10% and 20% of the cpu when it is not doing anything else than waiting for new tasks to appear. We are trying to implement a native postgreSQL storage using the LISTEN/NOTIFY[1,2] technology to correct that problem, so our first step was creating a native storage which for now it's just like the sequel one but directly on postgres. When we started this project we looked for some tests over the storage API and we didn't find anything, or at last anything up to date, so we also implemented some RSpec tests that can be used to test any storage, because it just ensures that the API conditions are fulfilled. Once the tests were done it was really easy to implement the storage and we tried it in a project with lots of tests and it works. If anyone wants to take a look at our first step, collaborate or comment something you'll find the project at github https://github.com/ifad/ruote-postgres thanks! [1]: http://www.postgresql.org/docs/9.0/static/sql-listen.html [2]: http://www.postgresql.org/docs/9.0/static/sql-notify.html -- -- 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.
