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
When having a large number of related benchmarks (in my case ~200), the perf plot does take quite a long time to load. This comes with Bencher Console becoming somewhat unresponsive.
Obviously, ~200 benchmarks are to many for a single plot at the same time, but Bencher supports hiding and unhiding plots - making it reasonable to hide all of them initially and offer the option to unhide relevant ones or even all of them when needed.
I would propose persisting the hide-state in a project's plots by making it accessible from the plot url. This would allow me to further customize plots in iframes too.
The text was updated successfully, but these errors were encountered:
@VanDulti thank you for using Bencher, and I'm sorry things aren't working as you expected.
The Perf Plots can support up to 255 permutations. However, as you've experienced this can take a while to load. I've done quite a bit of performance tuning on this front. Though I should probably take another look at it.
With that said, preventing this sort of usage was the primary motivation behind creating Pinned Plots. Have you tried setting up Pinned Plots instead of using one massive Perf Plot?
If so, what problems have you been running into and what makes you prefer the massive Perf Plot?
If not, could you help me understand why?
This would allow me to further customize plots in iframes too.
I'm curious, where are you using these iframes?
Is there a reason iframes for each set of the plot selections doesn't work?
When having a large number of related benchmarks (in my case ~200), the perf plot does take quite a long time to load. This comes with Bencher Console becoming somewhat unresponsive.
Obviously, ~200 benchmarks are to many for a single plot at the same time, but Bencher supports hiding and unhiding plots - making it reasonable to hide all of them initially and offer the option to unhide relevant ones or even all of them when needed.
I would propose persisting the hide-state in a project's plots by making it accessible from the plot url. This would allow me to further customize plots in iframes too.
The text was updated successfully, but these errors were encountered: