3 ms·
Presumably, the point of using WASM and service workers is for performance, but I see no benchmarks. I also have trouble imagining that this actually improves p
by bcherny 9y ago
Presumably, the point of using WASM and service workers is for performance, but I see no benchmarks. I also have trouble imagining that this actually improves performance, unless you’re doing all of your compute in the browser and it’s CPU bound (this seems like bad design).
What is the performance of doing it this way vs. without WASM and workers?
Until we see numbers, this smells like a recruiting play.
- texodus 9y agoWe use Web Workers principally to separate data CPU load from rendering load, as the datasets we deal with update very frequently and are quite large, and e.g. Highcharts can take on teh order of 100ms+ on detailed charts. We have some light benchmarks we use for regression testing, but definitely need more work in this area [benchmarks](https://jpmorganchase.github.io/perspective/examples/benchmark.html https://jpmorganchase.github.io/perspective/examples/benchma...)
- lucozade 9y agoFor ticking data being pushed into bespoke pivots, running this on the backend and, say, pushing renders to the frontend isn't generally better. You're not likely to be sharing much of the grunt. Also, latency will be an issue so you need to be pretty careful with GC runtimes that aren't optimised for latency. > What is the performance of doing it this way vs. without WASM and workers? @dman says in another thread that the original was in Python and this was 10x faster. If this met their performance goals, it does the job. It may be possible that another way is better, for some definition of better, but who cares if it works as required? > Until we see numbers, this smells like a recruiting play. It's presumably OK not to use it if you don't want to. And what if they think this may help recruiting? Seems like a reasonable trade to me.