A better approach would to remove the calls to NotifyPropertyChanged whenever the data changes.
Create a timer and refresh on the timer. That way you can control the refresh rate, and it is not bound to the rate at which the data arrives.
More Related Contents:
- MVVM: Tutorial from start to finish?
- Add n rectangles to canvas with MVVM in WPF
- Good or bad practice for Dialogs in wpf with MVVM?
- Set focus on TextBox in WPF from view model
- How to bind to a PasswordBox in MVVM
- Why RelayCommand
- How do I bind a TabControl to a collection of ViewModels?
- How to handle dependency injection in a WPF/MVVM application
- This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread [duplicate]
- Bind to SelectedItems from DataGrid or ListBox in MVVM
- How to implement a progress bar using the MVVM pattern
- Implementing CollectionChanged
- MVVM in WPF – How to alert ViewModel of changes in Model… or should I?
- MVVM Light & WPF – Binding Multiple instances of a Window to a ViewModel
- Binding an Image in WPF MVVM
- Give some command to View in MVVM
- How to support ListBox SelectedItems binding with MVVM in a navigable application
- WPF/MVVM – how to handle double-click on TreeViewItems in the ViewModel?
- WPF binding not updating the view
- Should I bind to ICollectionView or ObservableCollection
- Twoway-bind view’s DependencyProperty to viewmodel’s property?
- WPF: How to bind a command to the ListBoxItem using MVVM?
- Can I somehow temporarily disable WPF data binding changes?
- ObservableCollection not updating View
- The component does not have a resource identified by the uri
- MVVM – what is the ideal way for usercontrols to talk to each other
- Binding Commands to Events?
- How to have multiple pairs “View-ViewModel”?
- Accessing a property in one ViewModel from another
- Is it wrong to use the Dispatcher within my ViewModel?