You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
updating the sha256 hash for each chunk during unpack is slow - seems to take 6ms for every chunk
xz-decompress is slow
There may be overhead because for the XZ decompression and SHA calculation we transfer bytes from JS to WASM (and back for decompression)... Not sure yet how complex it is to write something to process everything on the WASM side.
Moving the QdlManager to a web worker (instead of just ImageWorker) may also help speed things up as it would move the flashing (which includes computations like Sparse.splitBlob) off of the main/render thread
Faster flashing of sparse images in qdl.js (flashing from 2:30 to 1:50)
fast erase partition/sector
skip chunks during flashing
Stream images to flash while downloading (qdl.js needs to accept a ReadableStream for blob to flash)
You can generate perf traces in Chrome in the performance tab
The text was updated successfully, but these errors were encountered:
js-sha
withhash-wasm
(unpack 10m -> 4m)xz-decompress
is slowQdlManager
to a web worker (instead of justImageWorker
) may also help speed things up as it would move the flashing (which includes computations likeSparse.splitBlob
) off of the main/render threadqdl.js
(flashing from 2:30 to 1:50)qdl.js
needs to accept aReadableStream
for blob to flash)You can generate perf traces in Chrome in the performance tab
The text was updated successfully, but these errors were encountered: