Web version
pgaskin opened this issue · 2 comments
pgaskin commented
Web version
pgaskin commented
The largest limitation will be WebAssembly's single-threadedness and the way content will need to be stored in-memory in an ArrayBuffer. Based on what I have so far in the pgaskin/wasm branch, with the zip117 build option, kepubify will have performance around 15% slower than running kepubify with a single thread locally. For example, a 0.2 second conversion on 8 cores would take around 1.85 seconds in a recent browser, while using around 2-3x as much memory for the same file.