Hi,
I have designed Ignite UI Angular 2 Grid and binding data from an API. I have successfully tested it and it works fine. I have around 500 records with 110 columns. I am not using Paging, have enabled filtering, row resizing, sorting, column fixing for first two columns and I am not using Lazy-loading. Initially I was using Google Chrome, for which the grid response was acceptable. Then I switched to IE (Specifically IE11) as my project requirement asks for it. The performance what I could observe was way too low. Even the scrolling had a visible delay. If I double click the cells for editing it also takes up some time to open . All this are seen without any validations or combo box for editing. I do understand the performance differs in each browsers based on how it handles the code, however Is there any possible tweaks which I can do to increase the performance in IE.
Regards
Rahul S
Hello Rahul,
Thank you for contacting Infragistics!
The first thing I would recommend is to take a look at your design and re-consider if your grid needs 110 columns. Are you users going to be able to process all that information or is a large part of it considered noise by them. Next you will want to look at where your bottle neck is. What is taking more time pulling down the data or rendering the grid? If it is the pull down I would recommend looking into remote paging or append rows on demand so that only the records you need for the current page are pulled:
https://www.igniteui.com/help/api/2017.1/ui.igGridAppendRowsOnDemand
https://www.igniteui.com/help/api/2017.1/ui.iggridpaging
https://www.igniteui.com/help/api/2017.1/ui.iggridpaging#options:type
If it is rendering then you could look into local paging or virtualization:
https://www.igniteui.com/help/api/2017.1/ui.iggrid#options:rowVirtualization
https://www.igniteui.com/help/api/2017.1/ui.iggrid#options:columnVirtualization