First -- people who read these messages as "threads" would appreciate it if you brought in a new topic by sending a new message to the group, rather than by replying to an existing message while changing the subject.
When you say "the process takes an age to complete" you're not giving information about what it is that's slow; perhaps you don't know. Normally, "an update to a section of the page" takes place by a postback to the form on the server; it runs any SQL logic and re-creates the page; the page the user sees is replaced by the new page. The work that "updates all the child nodes and all their child nodes" takes place on the server, not on the web page the user sees. Is the page appearing a lot more slowly than it would if you were going to the page the first time? If so, that suggests that it's the update activity in SQL that's slow. Making SQL code go faster is somewhat out of the scope of this forum (tho many would likely be happy to help). Do you know what SQL statements are being run? Do you know if they're slow? Can you reproduce the slowness in your test environment (where it would be reasonable to turn on the SQL Server Profiler)? Is it important that the user see the full set of updated results before continuing with their activity? Only if the answer to the last question is "no" might you be able to do things asynchronously to some advantage -- but doing so would involve more interactions between the browser and the server; if the web server is heavily loaded, that might hurt performance rather than help. It might matter what kind of controls are displaying the content. It might make an asynch approach to updating the content gradually, in asynchronous steps, much more difficult. As is often the case, more info is needed. At 12:28 PM 2/21/2007, Paul Cowan wrote >Hi, > >I wonder what my design options are for the following problem: > >1. We have an ASP.NET application that is a CMS. Part of the functionality >is that an update to a section of the page and then consequencely updates >all the child nodes and all their child nodes etc. >2. The application uses NHibernate for db interaction. >3. The site has now grown to such an extent that we are getting SqlTimeouts >as the process takes an age to complete. > >My question is what are my options? > >I can change the timeout but has this a very short term fix. > >Would calling this functionality asynchronously in anyway help? > >Cheers >[EMAIL PROTECTED] J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
