Replies: 1 comment 3 replies
-
How do you mean 'it gets stuck'? It's hard to comment on performance without seeing the specifics of your models and implementation. There is some discussion about refreshing plots and how it can go wrong in #1786; if you are queueing refreshes more quickly than they can be serviced, you will notice a significant reduction in responsiveness. Performance depends heavily on the platform and the plots themselves (e.g. a million data-points should be cheap if they are pretty much in a straight line or most of them are outside of the plot bounds, but if it's random X/Y noise will quickly become a problem; markers can be very expensive). If you have large data-sets, then it may be worth considering some sort of pre-processing to reduce the number of points rendered. |
Beta Was this translation helpful? Give feedback.
-
Hello, maintainer
I'm here again.
I would like to ask for some suggestion, because it has been bothering me for a long time. Can I use Oxyplot to process about 20-30 plots on a view and refresh the data every 500ms? there are about 10000 data on each plot.
In the process of writing my own code, I found that when the data is a little larger, it gets stuck. I don't know if there is a problem with my code or the performance of plot is not suitable?
Thank you very much. I like your project very much.
.Net5 OxyPlot 2.0 WPF
Beta Was this translation helpful? Give feedback.
All reactions