Best Practices: Display Large Data

  • 9 minutes to read

A chart’s performance directly relates to how many points and elements it displays: fewer elements result in higher performance. This topic explains how to reduce the number of data points and enhance the chart’s performance.

Load Data

The following approaches can help you to accelerate loading data:

  • Store all data points in as few series as possible. The Chart control is optimized to render a small number of series that have many points, rather than a large number of series with a few points. For example, a single series with a million points is processed faster than 10 series with 100000 points each.

  • Use data adapters to load data to the chart.

    You can automatically create series based on a template at chart level. To do this, initialize the SeriesTemplate.DataAdapter property with one of the following objects:

    To populate a manually created series with data, initialize the Series.DataAdapter property with one of the following objects:

  • If the data schema of the underlying chart source is known, create an adapter that loads data to the chart. The adapter implemented specifically for your data source allows you to avoid the overhead of the Reflection API and type boxing operations. To create a data adapter, create a class that implements ISeriesAdapter or ISeriesTemplateAdapter.

    For example, the chart’s data source is a collection of the following objects:

    public class DataItem { 
        public double Argument { get; } 
        public double Value { get; } 
        public DataItem(double argument, double value) { 
            Argument = argument;
            Value = value; 

    The data adapter that loads DataItem objects may look as follows:

    public class CustomNumericDataAdapter : ISeriesAdapter {
        readonly IList<DataItem> items;
        public bool DataSorted => true;
        public int ItemsCount => this.items.Count;
        public CustomNumericDataAdapter(IList<DataItem> items) {
            this.items = items;
        event NotifyChartDataChangedEventHandler IChartDataAdapter.DataChanged {
            add { }
            remove { }
        public object Clone() {
            return this;
        public double GetNumericalValue(int index, ChartDataMemberType dataMember) {
            switch (dataMember) {
                case ChartDataMemberType.Argument: return items[index].Argument;
                case ChartDataMemberType.Value: return items[index].Value;
            return double.NaN;
        public object GetSourceObject(int index) {
            return this.items[index];
        public ActualScaleType GetScaleType(ChartDataMemberType dataMember) {
            return ActualScaleType.Numerical;
        public DateTime GetDateTimeValue(int index, ChartDataMemberType dataMember) {
            throw new NotImplementedException();
        public string GetQualitativeValue(int index, ChartDataMemberType dataMember) {
            throw new NotImplementedException();
        public TimeSpan GetTimeSpanValue(int index, ChartDataMemberType dataMember) {
            throw new NotImplementedException();
        public object GetObjectValue(int index, ChartDataMemberType dataMember) {
            throw new NotImplementedException();

Data Aggregation

You can use the Data Aggregation functionality to configure a more compact and readable view for a large amount of data. When using data aggregation, the chart splits the x-axis into intervals (according to the measurement unit value), and automatically aggregates data for each interval using an aggregation function. The following images illustrate this feature:

Non-aggregated data Data aggregated by year
non-aggregated-chart aggregated-chart-data

Refer to the following help topic for more details: Data Aggregation.

Automatic Resampling

An internal data resampling algorithm allows the chart to avoid unnecessary operations when rendering series. The chart renders the minimum set of points required to display the correct series shape and form. The algorithm discards all points that have no effect on the output (for example, overlapped points). Every time the zoom level or visible data range changes, the chart re-calculates the minimum point set.

The resampling algorithm is in effect under the following conditions:

  • The Chart or series is bound to data. For more information, see the ChartControl.DataSource and Series.DataSource properties.
  • The data source contains more than ten thousand data points.
  • The series’s AllowResample property is set to true. Alternatively, you can use the ResamplingDataAdapter to resample series.
  • The series has numeric values, and its numeric, DateTime or TimeSpan arguments are sorted in ascending order. Note that series with qualitative arguments are not resampled.

The resampled data algorithm and aggregated data display technique optimize RAM usage, but aggregate calculations require additional time and the resulting series shape can be different from the original.

Note that the resampling algorithm is not supported for the following series views:

Automatic Calculations

Range, scale type and layout’s automatic calculations require additional resources. The following steps can help accelerate rendering a chart:

Rendering Visual Elements

Follow the steps below to decrease the time needed to render a chart’s visual elements:

Interactivity Optimization

The runtime hit testing, selection and tooltips features require additional CPU and RAM resources and may decrease performance.

Changeable Data

This section contains tips that allow you to increase performance when a chart shows a dataset that changes frequently.

  • Remove an existing point and add a new one instead to update the chart’s data. Changing an existing SeriesPoint‘s argument or value results in unnecessary calculations. For example, if you change the SeriesPoint.Values property, it calls the ChartControl.RefreshData method and updates the chart’s data.
  • Since v17.1, the Chart Control completely processes the following event arguments to avoid reloading all the data when the chart is bound to a dataset that updates frequently:

    For this reason, use the IBindingList objects to process data efficiently when a chart frequently updates data.

See Also