Today, workers usually run the JS engine of the host browser. So the performance should be approximately the same as the host.
It would be possible to use a different, faster JS engine, which is something we have discussed. In that case, you can still count on the workerpool performance being >= the native browser's JS engine performance. On Sun, Aug 31, 2008 at 6:09 AM, Samuel <[EMAIL PROTECTED]> wrote: > > HI, I am very intertesting in workerpool performance of Gears, any > recommendation on client benchmark which uses workerpool heavily? > > Thanks! > > Samuel >
