Investigate: Dip plot performance optimazation

[tomktjemsland]

Dip plot draws both shape and tail of hundreds of points. The current approach start struggling with more than 1000 points, and our test data have between 1000 and 1500, with an outlier at 3000.

We drop from 60 fps to 30 fps at 1500 points, and from 60 fps to 10 fps at 3000 points. This is on decent PCs.

This is only a problem at greater zoom-levels where ALL data is being rendered every frame, whether we zoom or pan.

Quick and dirty solution:

• Find and store closest N points of same type/color once when passing data to track. On each frame evaluate if each points body is overlapping or near overlapping with another point, if so, draw only tail.

Better long term solution:

• Move from Canvas 2D to a WebGL-based solution, such as PIXI.

[GuillaumeVix]

Lets start with having a look at the Dip logs potential optimization.
Any win on the logic / processing side?

Wait for users to complain before looking at it