Configurable dynamic plot aggregation based on zoom-level

[teh-cmc]

⚠️ Try it live! ⚠️

Make it so users can configure an aggregation strategy in the rare case where they either have so much data or are so zoomed out that most of their plot results in an overdraw blurb.

Because this builds on top of the range cache, the data is neatly laid out in a memory slice already so this is very cheap to compute.

In my tests, the MinMax strategy has worked so well that I've decided to make it the default in the end... That might be controversial 😶.

Off vs. MinMax, using the new gaussian walk benchmark:

• Fixes Configurable aggregation behaviors for time series plots #4271
• DNR: requires Primary caching 19 (final): de-staticify cache globals #4856

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using newly built examples: app.rerun.io
  • Using examples from latest main build: app.rerun.io
  • Using full set of examples from nightly build: app.rerun.io
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

• PR Build Summary
• Docs preview
• Examples preview
• Recent benchmark results
• Wasm size tracking

[nikolausWest]

I couldn't really spot the differences in the video. Btw, what does MinMax actually do? I would have assumed it output two values, a min and a max.

[nikolausWest]

As we present this option to users (both in the SDK and in the UI) I think it's important we clarify that this is about aggregating when we have multiple points per pixel in the plot

[teh-cmc]

I couldn't really spot the differences in the video. Btw, what does MinMax actually do? I would have assumed it output two values, a min and a max.

It's exactly what it does, and that results in a line that goes straight up between those two points, since they both live in the same "pixel column".
The result is effectively indistinguishable from what the non-aggregated path would do in many cases, except we get there without any overdraw.

[teh-cmc]

As we present this option to users (both in the SDK and in the UI) I think it's important we clarify that this is about aggregating when we have multiple points per pixel in the plot

This is what the hover says at the moment:

[github-actions]

Size changes

Name	main	4865/merge	Change
plots.rrd	204.80 kiB	194.56 kiB	-5.00%

[nikolausWest]

This is pretty sweet!

[emilk]

Awesome ⭐

[emilk]

faster, less hacky

Suggested change

	egui::Id::new(format!("plot_{space_view_id}"))
	egui::Id::new(("plot", space_view_id))

[teh-cmc]

don't