Questions about the Large Object Heap size

[IVCSoft]

I was monitoring the .Net memory “Large Object Heap size” when plotting a TeeChart using the HighLow series. When plotting only with a few thousand points, the Large Object Heap size goes down to the initial value (i.e. a low value) after a myHighLow.Clear() call. When plotting with tens of thousand points, the Large Object Heap size does NOT go down to the initial value (i.e. a low value) after a myHighLow.Clear() call. The Large Object Heap size does reduce, but remain as a high number.

My first question is:
Why the myHighLow.Clear() call does not clean the Large Object Heap size largely after plotting a large data set?

The second question is:
Will the remaining high number of the Large Object Heap size affect the speed of loading the next data set?

Thank you,
Michael

[Narcís]

Hi Michael,

Code: Select all

Will the remaining high number of the Large Object Heap size affect the speed of loading the next data set? 

Have you tried this? If this is still a problem we will investigate this issue.

[IVCSoft]

Hi Narcis,

I can not see your code, and did not understand your reply.

Thanks,
Michael

[Narcís]

Hi IVCSoft,

Sorry if I wasn't clear enough. I was asking if you had been able to reproduce what you asked in your second question.

Thanks in advance.

[IVCSoft]

Hi Narcis,

Sure. What I observed can be reproduced.

My goal is to speed up the loading and graphing of several High-Low series.

My charting operation involves reading a data file with multiple channels, finding the maximum and minimum, and composing the High-Low series.

Using a single file, I have also observed most of times the first loading/graphing after the fresh start of the application is much slower than those of the second or the third times. Surprisingly, in few tests, the first loading/graphing after the fresh start of the application is just as speedy as the second or later times. How can I attain the speedy performance very time? Can you shed some light on this issue?

All these tests were run on the same computer with the very similar resources. Each loading operation will have the myHighLow.Clear() call in the beginning. What does the myHighLow.Clear() call touch the memory?

Thanks again for your help,
Michael

[Narcís]

Hi Michael,

Thanks for the information. Then you may be interested in reading this MSDN's article and you can also download Lutz Roeder's .NET Reflector to study individual method calls, ...