> is broken on mobile

Not true as of last deployment.

> but zero technical detail

What additional technical detail would you be interested in?

> Also seems a couple orders of magnitude slower than what I’d expect even for a single core.

1) it's more than 2m/s on a MacBook AIR 2) Most of the latency is networking. This was a preliminary setup with a client / server over websockets where the book of 1m contracts combination of (strike, exp_date). Each insert only after a corresponding query has been returned (over the wire) from the previous insert. I can agree the eval isn't great; as in, the throughput is much higher.

> What exact transformations are being done

This is provided in the blog post.