fix mouse interaction performance for 2,000 series

[leeoniya]

this is a retro issue to illustrate the performance gains of the new cursor.points.one: true setting with a large amount of series (2k series * 1k points each). the commits were:

• b7c8eca
• 84a3835
• b9a7ce9

uPlot currently draws live cursor hover points using dom elements to avoid clearing and redrawing the main canvas on every mousemove event. this strategy may change in the future to utilize a second canvas, but that's a longer-term project: #922. anyways, the DOM method works well for a sane amount of series (< 100). however, there are users of Grafana that throw some pretty insane datasets at uPlot - like 2,000 series. since uPlot always creates one dom hover point per series, this now translates to 2,000 dom elements updated on every mouse move.

even after we disable the massive/useless live legend (also in the dom), we still have obvious super badness. 10s of continuous mousemoves results in only 570ms of browser idle time, with heavy UI lag and cpu burn:

---

a new cursor.points.one: true option switches uPlot to only create a single hover point which is reused across all series and only shows up for the closest hovered series and data index. how does it do that? it relies on the series focus functionality that uses proximity setting, so you also need to set cursor.focus.prox >= 0, and if you dont want series dimming, also focus.alpha: 1.

additionally, the first listed commit disables formatting values with a static or disabled legend.

with these settings and legend disabled we now have 8935ms of browser idle time and no perceivable UI lag 🎉

[leeoniya]

on the Grafana side...

original:

---

cursor.points.one: true:

---

cursor.points.one: true + newVizTooltips feature flag: