3 ms·

This is a really great interface, and cool idea. You might consider upping the run count, or maybe narrowing your bins for the visualization. Either way, it's

• minimaxir 11y ago
  5,000 tests is more than enough for most general use cases. (i.e. data that would be able to fit into browser memory, anyways)
• ozgooen 11y ago
  In practice, 5000 was basically the number that wouldn't slow it down; this represented around 20-30% of the rendering time (react components were the main bottleneck, surprisingly, though I could still optimize them more). I think that this works fine for small models, which is much of what exists now. As there are larger models, I'd eventually like to offload calculations to AWS Lambda or something similar, so we can do far more.