Comment #4 on issue 955 by michael.glasten: blob.getBytes and blob.slice
performance issues in Chrome
http://code.google.com/p/gears/issues/detail?id=955
Implemented this trough a worker. Still takes about a minute to read 1Mb in
Chrome.
The only benefit of using the worker is that the UI is not frozen and no
"unresponsive script" alerts are shown.
There is more here than just cross-process performance issues.
getBytes() returns quickly in the first several steps, but as the loop
progresses, it
takes more and more time (specifically in Chrome). With random access
files/blobs it
should not matter whether you read at the beginning of the file or at the
end. Thus I
suspect that internally (only in Chrome?) access is done sequentially,
otherwise
there is no reason why accessing 1000-th block should be much slower than
10-th.
--
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
