如何在WPF中用ListView/GridView实时显示大量CAN总线数据

针对每秒60条的CAN消息导致UI阻塞的问题，结合你的虚拟化集合和MVVM架构，可通过以下几个关键优化点解决：

1. 替换ObservableCollection，实现自定义批量更新的虚拟化集合 #

ObservableCollection每条消息都触发CollectionChanged会导致UI频繁更新，而BindingOperations.EnableCollectionSynchronization的ShadowList会抵消虚拟化优势。我们需要实现一个支持批量更新、线程安全的自定义虚拟化集合：

public class VirtualizingCanMessageCollection : VirtualizingCollection<CanMessage>, INotifyCollectionChanged
{
    private readonly object _syncLock = new object();
    private readonly List<CanMessage> _pendingBatch = new List<CanMessage>();
    private readonly Timer _batchTimer;
    private const int BatchIntervalMs = 100; // 每100ms批量更新一次，平衡实时性与性能
    private const int MaxDisplayCount = 1000; // 限制最大显示条数，避免集合无限膨胀

    public VirtualizingCanMessageCollection()
    {
        _batchTimer = new Timer(ProcessPendingBatch, null, 0, BatchIntervalMs);
    }

    // 后台线程调用，添加新消息
    public void EnqueueMessage(CanMessage message)
    {
        lock (_syncLock)
        {
            _pendingBatch.Add(message);
            // 超过最大条数时提前移除旧消息
            while (Items.Count + _pendingBatch.Count > MaxDisplayCount)
            {
                Items.RemoveAt(0);
            }
        }
    }

    private void ProcessPendingBatch(object state)
    {
        List<CanMessage> currentBatch = null;
        List<CanMessage> removedItems = null;

        lock (_syncLock)
        {
            if (_pendingBatch.Count == 0) return;
            
            currentBatch = new List<CanMessage>(_pendingBatch);
            _pendingBatch.Clear();

            // 处理超出最大条数的情况，记录移除的项
            var overflowCount = Items.Count + currentBatch.Count - MaxDisplayCount;
            if (overflowCount > 0)
            {
                removedItems = Items.Take(overflowCount).ToList();
                Items.RemoveRange(0, overflowCount);
            }
        }

        // 批量添加新消息到集合
        foreach (var msg in currentBatch)
        {
            Items.Add(msg);
        }

        // 在UI线程统一触发CollectionChanged事件
        Application.Current.Dispatcher.Invoke(() =>
        {
            if (removedItems != null)
            {
                CollectionChanged?.Invoke(this, new NotifyCollectionChangedEventArgs(
                    NotifyCollectionChangedAction.Remove, removedItems));
            }
            
            CollectionChanged?.Invoke(this, new NotifyCollectionChangedEventArgs(
                NotifyCollectionChangedAction.Add, currentBatch));
        });
    }

    public event NotifyCollectionChangedEventHandler CollectionChanged;
}

2. 禁用实时自动列宽计算 #

AutoSizingGridView的实时列宽计算是UI线程的高耗时操作，高频更新时会严重拖慢UI。改为手动触发列宽调整：

public class OptimizedAutoSizingGridView : GridView
{
    public void RefreshColumnWidths()
    {
        foreach (var column in Columns)
        {
            // 先设为自动计算，再固定为实际宽度
            column.Width = GridViewColumn.Width.Auto;
            column.Width = column.ActualWidth;
        }
    }
}

在ViewModel中，可设置定时任务（比如每5秒）调用一次RefreshColumnWidths，或者提供按钮让用户手动触发，而非实时更新。

3. 确保ListView虚拟化完全生效 #

检查XAML配置，确保虚拟化的关键属性正确设置：

<ListView ItemsSource="{Binding CanMessages}"
          VirtualizingStackPanel.IsVirtualizing="True"
          VirtualizingStackPanel.VirtualizationMode="Recycling"
          ScrollViewer.CanContentScroll="True"
          ScrollViewer.IsDeferredScrollingEnabled="True">
    <ListView.View>
        <local:OptimizedAutoSizingGridView>
            <!-- 你的列定义 -->
            <GridViewColumn Header="ID" DisplayMemberBinding="{Binding Id}" />
            <GridViewColumn Header="Data" DisplayMemberBinding="{Binding Data}" />
        </local:OptimizedAutoSizingGridView>
    </ListView.View>
</ListView>

• VirtualizationMode="Recycling"：复用UI元素，减少创建/销毁开销
• ScrollViewer.CanContentScroll="True"：虚拟化生效的必要条件
• IsDeferredScrollingEnabled="True"：滚动时暂停数据更新，提升滚动流畅度

4. 手动控制线程同步，放弃BindingOperations.EnableCollectionSynchronization #

自定义集合中已通过lock和Dispatcher实现线程安全，不需要启用EnableCollectionSynchronization，避免ShadowList导致的虚拟化失效。

内容的提问来源于stack exchange，提问作者KingSB