| Dart Home | PowerWEB LiveControls for ASP.NET | Custom Development | Reply | PowerWEB LiveControls for ASP.NET Topics | Forums |
| Author | Forum: PowerWEB LiveControls for ASP.NET Topic: LiveDataGrid Version 1.4.1 |
| Clive cjenkins@postcentral.com From: Rochester, NY USA Posts: 29 Member Since: 07/13/05 |
posted June 23, 2006 4:27 PM Hi again, I am having some difficulty understanding why I am seeing a difference in performance with LiveDataGrid if I do a normal postback compared to a live callback - the routines that get run to populate my dataset, modify various attributes of each row(Color etc) - are the same, but a postback completes the process in under 1 sec with 18 records, where a liveTimer callback with update all turned off is taking 28 secs to do the same thing. I am sure it must be something that I'm doing wrong, but I cannot work out why I am getting this difference between the two types of calls. There is routine for coloring rows, enabling other row controls (non-live Labels and a non-live checkbox), etc. but it is the same routine that runs during a callback or a postback. It simply iterates through each row of the LiveDataGrid and sets the color and disables the checkbox based on various flags in the associated dataset. The performance hit seems dramatic, so do you have any idea what I may be doing wrong from what I described? cheers Clive |
John Talarico From: Rome, NY USA Posts: 630 Member Since: 06/01/05 |
posted June 26, 2006 11:23 AM Without being able to fully trace the application, it would be difficult to determine the root cause. However, your description gives me a few clues. The actual number of rows and amount of data are not the likely culprit, but the routine for coloring rows and enabling/disabling items may be part of it. When elements are updated in a callback, client-side script is generated to update page elements. If this manipulation is complex or lengthy, because the script engine is doing the work it may not be performing well. In a standard grid that issues a postback, the elements are rendered on the server and the resultant HTML is just interpreted on the client. |
| Clive cjenkins@postcentral.com From: Rochester, NY USA Posts: 29 Member Since: 07/13/05 |
posted June 26, 2006 12:38 PM Hi John, Thanks for the quick response! I think you've hit on what's actually happening. There are many enable/disable/color decisions made depending on the resulting dataset - and I am doing quite a bit of checking server-side to try and minimise the amount of changes that get sent to the grid on the client. I'm going to go through my code a bit more to try and see if I can make it a bit more efficient in this case. Thanks again Clive |
| Reply | PowerWEB LiveControls for ASP.NET Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|