Performance issue with a lot of data with TeeChart for .Net v2023

[David N.]

Hello,

After upgrading my project from the 2016 version to the 2023 i am experiencing the following two problems:

First, when i plot a lot of data the graphic starts to get a bit laggy you can see what happens when we try to Zoom. As well, the NearestPoint Event to the mouse starts to be a bit unresponsive. With the 2016 version this was not a problem:


The second problem that i have experienced with the 2023 version is that some line maks are not drawn, we have marked with red boxes where they should supposed to be:

And using the 2016 version you can see what am i expecting in the red boxes above (the blue lines):

[Christopher]

First, when i plot a lot of data the graphic starts to get a bit laggy you can see what happens when we try to Zoom. As well, the NearestPoint Event to the mouse starts to be a bit unresponsive. With the 2016 version this was not a problem:

I've been updating our benchmark speed tests which you can try yourself by downloading our example repo—these are build using Windows Forms, one set for net6.0 and the other for net472 and net48. The results we get here are as follows:
net6.0

Code: Select all

// * Summary *

BenchmarkDotNet=v0.13.5, OS=Windows 11 (10.0.22621.1848/22H2/2022Update/SunValley2)
11th Gen Intel Core i5-11400 2.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET SDK=7.0.400-preview.23274.1
  [Host]     : .NET 6.0.18 (6.0.1823.26907), X64 RyuJIT AVX2 [AttachedDebugger]
  DefaultJob : .NET 6.0.18 (6.0.1823.26907), X64 RyuJIT AVX2


|       Method |     Mean |   Error |  StdDev |
|------------- |---------:|--------:|--------:|
| RepaintForm1 | 274.5 ms | 2.32 ms | 2.17 ms |

// * Warnings *
Environment
  Summary -> Benchmark was executed with attached debugger

net472

Code: Select all

  // * Summary *

BenchmarkDotNet=v0.13.5, OS=Windows 11 (10.0.22621.1848/22H2/2022Update/SunValley2)
11th Gen Intel Core i5-11400 2.60GHz, 1 CPU, 12 logical and 6 physical cores
  [Host]     : .NET Framework 4.8.1 (4.8.9166.0), X86 LegacyJIT [AttachedDebugger]
  DefaultJob : .NET Framework 4.8.1 (4.8.9166.0), X86 LegacyJIT


|       Method |     Mean |    Error |   StdDev |
|------------- |---------:|---------:|---------:|
| RepaintForm1 | 11.05 ms | 0.212 ms | 0.253 ms |

// * Warnings *
Environment
  Summary -> Benchmark was executed with attached debugger

net48

Code: Select all

// * Summary *

BenchmarkDotNet=v0.13.5, OS=Windows 11 (10.0.22621.1848/22H2/2022Update/SunValley2)
11th Gen Intel Core i5-11400 2.60GHz, 1 CPU, 12 logical and 6 physical cores
  [Host]     : .NET Framework 4.8.1 (4.8.9166.0), X86 LegacyJIT [AttachedDebugger]
  DefaultJob : .NET Framework 4.8.1 (4.8.9166.0), X86 LegacyJIT


|       Method |     Mean |   Error |  StdDev |
|------------- |---------:|--------:|--------:|
| RepaintForm1 | 336.3 ms | 5.52 ms | 5.16 ms |

// * Warnings *
Environment
  Summary -> Benchmark was executed with attached debugger

As you can see, the results of net472 claim that this assembly is nearly 25 times faster than the second fastest assembly, the net60 assembly. We do not find this result credible, and in fact when running the net472 speed test we can see that the Chart, for some reason unknown to us, is not painting correctly.

Interesting though is the comparison between the net60 assemblies and the net48 assemblies—interesting because the code is identical, and in fact the .NET Standard 2.0 assembly with the platform-agnostic TeeChart API in it is the same assembly. The results indicate that the net6.0 assemblies run faster in Windows Forms that the net48 assemblies, indicating if anything an increase in performance of net6.0 Windows Forms over net48 (and .NET Framework in general, possibly) Windows Forms.

The second problem that i have experienced with the 2023 version is that some line maks are not drawn, we have marked with red boxes where they should supposed to be:

If you would be so kind, we're going to need a Minimal, Reproducible Example to be able to reproduce this issue with precision at our end and try to fix it for you. We have a location on our website where you can upload a zip file with your project.