Hi,
we are using the Xamdatagrid control (Verison: 11.1.20111.273) for our application. In almost all cases the grid runs smoothly but one of our customer has big performance problems with the grid on some PCs. The Rendering of the grid takes over 4 Minutes für nearly 1000 data records and 20 columns. When we set only one column visible the performance is ok but by setting more columns visible the perfomance drops enormously.
What we already have tried:
-Install newest video driver
-Reinstall .Net Framework and DirectX
-Set software rendering for the application
-Disable WPF font Cache Service
The Hardware specs of the affected Pcs are:
32 Bit Windows 7 SP1
Intel i3-2100 3.1 Ghz
4 GB RAM
Nvidia NVS 300 video card
Have you got a idee what can cause this performance issue?
regards
Hase
Hello Hase,
I don't recognize that version number. The latest 11.1 version is 11.1.20111.2282.
Have you tried profiling the application to see where in code the majority of those 4 minutes is taking place? 1000 records and 20 columns doesn't seem like a lot although columns in the XamDataGrid are not virtualized so it will render all of those columns for every visible row. Are you doing anything else to the grid, such as filtering or grouping?
I threw together a very basic sample that loads a XamDataGrid up with 1000 records and 20 columns. It displays in just a couple of seconds. Can you modify my sample to reproduce your issue or send me an existing sample you might have that reproduces this? That way I can try investigating where the performance issue is occurring.
Sorry,
we are using die Version 12.1.20121.1010. We don't see the code before the 4 Minute but aber that time "RecordsInViewChanged" is executed and the rendering is done.
Which event handler are executing before RecordsInViewChanged ?
As I said this Performance issue only appears on some Pcs of one customer. Other Pcs are running smoothly. In some cases we have over 50K Datarecord an the Performance is ok.
Yes we are filtering and grouping records. The same Problem appears also when we set or delete a filter on the ui.
I can't modify the example because we are not able to repoduce this behavio but i can try to run your example on the customers pcs.
thanks