Databases
StackOverflow2013
Postsdbo
POMost performant way to graph thousands of data points with WPF?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMost performant way to graph thousands of data points with WPF?
    primarykey
    data
    text
    <p>I have written a chart that displays financial data. Performance was good while I was drawing less than 10.000 points displayed as a connected line using <code>PathGeometry</code> together with <code>PathFigure</code> and <code>LineSegment</code>s. But now I need to display up to 100.000 points at the same time (without scrolling) and it's already very slow with 50.000 points. I was thinking of <code>StreamGeometry</code>, but I am not sure since it's basically the same as a <code>PathGeometry</code> stroring the information as byte stream. Does any one have an idea to make this much more performant or maybe someone has even done something similar already?</p> <p>EDIT: These data points do not change once drawn so if there is potential optimizing it, please let me know (line segments are frozen right now).</p> <p>EDIT: I tried StreamGeometry. Creating the graphic took even longer for some reason, but this is not the issue. Drawing on the chart after drawing all the points is still as slow as the previous method. I think it's just too many data points for WPF to deal with.</p> <p>EDIT: I've experimented a bit and I noticed that performance improved a bit by converting the coordinates which were previously in double to int to prevent WPF anti-aliasing sub-pixel lines.</p> <p>EDIT: Thanks for all the responses suggesting to reduce the number of line segments. I have reduced them to at most twice the horizontal resolution for stepped lines and at most the horizontal resolution for simple lines and the performance is pretty good now. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMost performant way to graph thousands of data points with WPF?
      1. USReed Copsey
      1. VTFavorite
    2. VO
      singulars
      1. POMost performant way to graph thousands of data points with WPF?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMost performant way to graph thousands of data points with WPF?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWith so many points on the screen at one time (i.e. I would think it'd be difficult to discretely identify all of them by eyes alone) couldn't you optimize the points prior to drawing (e.g. when several points form a "straight line", remove the "in-between" points and keep the "end-points")? This would reduce the points to draw, thus reducing the time to draw.
      singulars
      1. POMost performant way to graph thousands of data points with WPF?
      1. USMichael Todd
    2. COThanks Michael, I will try that.
      singulars
      1. POMost performant way to graph thousands of data points with WPF?
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload