Comment #1 on issue 955 by nigel.tao.gnome: blob.getBytes and blob.slice
performance issues in Chrome
http://code.google.com/p/gears/issues/detail?id=955
Yeah, I'm not surprised that performance sucks, since Gears methods like
concat and
getBytes have to cross a process boundary, with Chrome's multi-process
architecture.
Given that you can pass Blobs between workers, and IIRC a Chrome/Gears
worker computes
in the Gears process, then try passing the Blob that you get from
desktop.openFiles to
a worker, do the concat/getBytes in the worker, and pass the result back to
the main
thread.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
