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
Using multiple web-workers isn't free, since there's overhead when starting them and also overhead when sending data to/from workers; hence there might not be much of a performance improvement overall. Furthermore, using multiple web-workers would significantly increase the complexity of the code and might also introduce various edge-case problems.
Can I actually make a demo and demonstrate the performance improvements,
Please note that #18647 (comment) mentions a number of potential issues, hence a standalone demo probably isn't very helpful. (And once again: please refrain from needlessly tagging users, since that creates notification spam.)
Also, since this is just a word for word copy of k-yle/pdf-to-img#238 it seems that maybe your issue is actually with Node.js since it doesn't support web-workers. (We won't add support for the Node.js "Worker threads" concept in the PDF.js library.)
Is the feature relevant to the Firefox PDF Viewer?
No
Feature description
I think using multiple workers(worker threads in node or webworkers in browser) to render canvases using offscreen canvas (https://web.dev/articles/offscreen-canvas#use_with_popular_libraries) (https://web.dev/articles/offscreen-canvas) actually increases the speed exponentially as rendering/drawing these canvas actually taking a lot time
Other PDF viewers
No response
The text was updated successfully, but these errors were encountered: