HI,
My ultragrid is bound to a binding list of objects.when i scroll the grid the cpu usage of my application is going up by 50%.The number of rows in the application when i observed this behaviour was about 250.There is nothing i'm doing when the grid scroll event fires.Is there some thing that i could do to better the situation??
Regards,
Vj
Well, my first question is, why does it matter? Why do you care if scrolling the grid requires a lot of CPU usage? Painting the grid with multiple bands is certainly going to be more complex than painting a single band, regardless of the number of rows. Why does this cause a problem?
The most likely issue here is that it's simply the complexity of the painting of the grid and all of it's UIElements. In that case, some of the suggestions in the WinGrid Performance Guide should help. In particular, the sections on Painting, ValueLists, and CellDisplayStyle should be particularly effective. If you have tried everything in the performance guide and none of it makes any difference, then I would encourage you to create a small sample project that demonstrates the issue and Submit an incident to Infragistics Developer Support so they can check it out.
I am also facing same issue I expand child bands or scroll expanded bands. Does anybody has solution for it?
Hello,
I have noticed the same issue with WinGrid. I am using an UltraDataSource where there are two bands of data - a main one and child one. The child band has one or more rows associated with a single row in a the main band. While scrolling using the mouse wheel the CPU utilization will shoot up to 50%. This seems to occur when both bands are in the viewing area. If there is a long stretch of rows in the child band the mouse scrolling is fast and CPU utilization is low, but when the is a collection of main and child band rows visible the performance suffers.
I don't see this issue with the exact same data when only a single main band is used. There is the same number of rows and columns. Scrolling with the mouse wheel is fast and CPU utilization is low.
I looked at the WinGrid performance suggestions and don't see any that apply. I tried breaking the application while in Visual Studio, but is always stops on the "ShowDialog" call (the WinGrid is on a dialog) and never in any dialog code.
Any suggestions?
Thanks.
DJ
Hi,
It's impossible to guess without knowing what your application is doing. But perhaps you should check out the WinGrid Performance Guide