Forums Retired Products and Controls
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Akshay
300
How-to Get Best Performance With Large Amount Of Data
posted

Hi,

    We are using Infragistics controls in our project. We are really concerned about the performance of the controls espically the UltraWebGrid which we are using. There is a huge amount of data that is being displayed in the grid(more than 400 rows and 80 columns) and lots of client side functionalities also. Presently the performance is really poor. Please suggest some ways to increase the performance.

I just wanted to know something about the infragistics support. Like

1. How fast the queries are answered?

2. If we want some additional functionalities to be implemented then is it possible for you people to implement it or not and if yes then how much time will it take?

3. The project we are working on is a really big one and requires a very good perfomance. Will infragistics UltraWebGrid and other controls be able to provide such a good performance?

 

Akshay

Parents
No Data
Reply
  • 821
    Offline posted

    - It can also help alot if you try to use short identifiers of css class names, element ID's, Javascript Functions, etc. Especially when u have large grids with lots of columns and rows.

    - Check out the  "OptimizeCSSClassNamesOutput" property this does what i described directly from Infragistics, so the grid renders more Compact.

    - Setting style/appearance property at top most level
    We in our company make really heavy use from Infragistics Appearances in our Fatclient, and we had to port this to web. So pay attention how you build your Grid on the server side. Keep the defaults in mind and set the stuff on the server side only exactly when its needed. If you iterate through cells in the Webgrid on server and set some style/appearance properties, this will have a direct inpact to the html. Because then everycell has the style directly set (not through CSS identifiers). Never set any properties on a level where you can set a property on a parent level. (If the row itself has backcolor=red, avoid setting it on the cell) I know this sounds simple and clear but its very important to always keep this in mind. A wrong implemented appearance on server side can heavily destroy performance.
    We get so far in our company that we created "CSS styled" appearance merge logic for infragistics appearances... 

Children
No Data