I find it rather unbelievable that adding an intermediary proxy layer to implement asynchronous PHP will 'accelerate' any script unless it's running on a *very* heavily overloaded and poorly optimized server.
Using native PHP, if you have say four database calls that block each other, you could use the session or a separate database table or even a memcache variable to communicate status messages between the scripts. This way there's no middle man, no extra memory usage for a proxy layer and a completely native implementation not influenced by any PHP libraries that may be incompatible with callback functions.
Manuel Lemos - 2010-11-01 23:42:30 - In reply to message 1 from David Gibbons
There seems to be a misunderstanding.
The only case on which calling a parallel process using Gearman was suggested is to overcome current PHP limitations of database access extensions that only allow synchronous calls.
It would be faster calling processes asynchronously because you would be able to make multiple calls without having to wait for one before proceeding to the next.