Thanks for the explanation. We can't use sparse sampling either because they want all the data to be visible. Once I converted my application to x64 I was able to plot 110 million data points on a plot and I had 2 plots (220 million data points in total). The application grew to 16GB but it still ran without crashing, this test was probably 2X more than we would see in the field. Once I ran it with a normal data set of 50 million per plot it grew to 7GB and is a little sluggish when resizing, but I don't think the end user would be too unhappy with it.
If you have a solution for this problem, I could cut my data points in half. I have to be able to draw the data points in red and then about halfway through I need to draw them in blue but leave the first half red. The only way I've found to do this so far is to have 2 graphs on the plot and the invisible one is plotting qNan() until it is needed and then they flip, but this causes twice as many points.
Or is there an easy way to store some of the data to disk instead of having it all in RAM? I'm worried not all the PCs that will run this application will have enough memory.
This is an awesome library to work with. It does almost anything you need it to, that's why I'm thinking I'm missing something simple that I haven't found yet.
Thanks for all of your hard work!