Hi,
I'm upgrading from UltraWebGrid to the new WebDataGrid and I've been dealing with significant performance issues in IE8. The grid has about 45 columns and 100 rows. In UltraWebGrid, this was not an issue. However, the new grid takes 2-3 times as long to load (~10 seconds), and selecting a cell literally takes ~5 seconds compared to ~.5 seconds in the old grid. The grid performs poorly in Firefox as well - only Chrome seems to provide good performance. However, I need it to work in IE8. The exact version of IE is 8.0.7601.17514.
Also, paging isn't really an option based on the business requirements, but shouldn't the new grid perform better anyway?
Thanks,
Mike
Hello Mike,
Thank you for contacting Infragistics!
We received your support request concerning Performance issue in IE8, and this case has been assigned to me. Infragistics is dedicated to helping you solve this issue. Our team and I have done an initial review of your case and I have the following questions; a.) What is the version you are using?b.) What service release are you using?c.) Have you tried the Virtual Scrolling behavior?
For further information concerning virtual scrolling please see the following:http://help.infragistics.com/NetAdvantage/ASPNET/2012.1/CLR4.0/?page=WebDataGrid_Virtual_Scrolling.html
Looking forward to hearing from you,
Sincerely,Mike P.Developer Support EngineerInfragistics, Inc.www.infragistics.com
a/b) I'm using version 12.1 of NetAdvantage, and I'm using the 3.5 version of the assembly (Infragistics35.Web.v12.1.dll), with runtime version v2.0.50727
c) Yes. Virtual scrolling does improve the performance slightly, but it's still nowhere near the old UltraWebGrid.
Hi Mike,
Thanks for your response. I'm unable to currently isolate the problem that causes the issue. I have attached a grid that more accurately represents my own - however I don't know how helpful it will be to you without more information. I cannot reproduce the issue with the WebApp I attached. The sample you provided does not reproduce this issue either.
The service release I'm using is the same as the one you mentioned: 12.1.20121.2072. My firefox is version 15.0.1 and Chrome (the only browser this doesn't happen in) is version 22.0.1229.94.
The setup of the page in question is pretty close to the WebApp I've attached. It inherits from a master page to get some header controls, a footer, and a css file. Other than that it's just an asp:DropDownList to filter the view (also in the attached) and the grid. The page pulls from a database instead of hard-coded data, but this shouldn't have an effect since the old grid still performed better and pulled the same data.
The page loads in a very similar way to the old grid. The difference is when the new grid is rendered on the page, after the OnLoadComplete event is triggered. IE8 freezes for 2-10 seconds, and everything on the page except the grid is visible during this time. The loading bar is almost completely full. Interaction with the page is impossible during this time, although IE8 still seems to be responding (the page does not white-out when you click it to indicate that it's frozen). Once the grid renders it's fairly similar to the UltraWebGrid in performance, except that selecting a cell is still very slow compared to the old grid. There are no custom events or anything tied to this - the grid is read-only.
I will continue to hunt for the problem, but any additional help you can offer is useful.
Hello Michael,
Thank you for your patience. I have done some further looking into this matter and I have been unable to reproduce this behavior in IE8, IE9 or Firefox. I am attaching my sample demonstrating this. Can you please run it and see if you see the same behavior. I am using 12.1.20121.2072 which is the latest service release for v12.1. Can you please check the full version number of 12.1 you are using? You can find this in the web.config or aspx page. Can you tell me more about the setup of your page and grid? Do you have an isolated sample that reproduces this behavior? Can you please provide me with an isolated sample that reproduces this behavior? What version of Firefox are you using?