Describe the bug
For each point that is drawn there are a couple places where it references MaxValue. Unfortunately, MaxValue has a linq statement that goes over every point to to determine the max value. For small datasets this is not noticeable, but for large data sets this becomes problematic fast.
Which platform and version is this for?
Latest codebase
To Reproduce
Steps to reproduce the behavior:
Create a chart with a large number of data points
Expected behavior
Move the calculation of MaxValue out of the loop so it the value can be cached per render
Additional information
I'm working on a PR for this: Working Branch
Describe the bug For each point that is drawn there are a couple places where it references MaxValue. Unfortunately, MaxValue has a linq statement that goes over every point to to determine the max value. For small datasets this is not noticeable, but for large data sets this becomes problematic fast.
Which platform and version is this for? Latest codebase
To Reproduce Steps to reproduce the behavior:
Expected behavior Move the calculation of MaxValue out of the loop so it the value can be cached per render
Additional information I'm working on a PR for this: Working Branch