Thanks Russell. This is good information. I am going to evaluate the server side activity first and then will look into any inefficiencies on the client.
J.D. -----Original Message----- From: Russell Morrisey [mailto:[email protected]] Sent: Thursday, February 25, 2010 11:39 AM To: [email protected] Subject: RE: Speeding Up HTML Parse??? Before spending a lot of time trying to debug client-side performance, be sure that the problem is on the client side, and not the server. A lot of performance problems I see on my project arise from user code on the server side which takes a long time to run (such as redundant or inefficient database hits). If you do find that the problem is client-side, a couple of ideas of things to look for: -Excessive/redundant javascript. Externalize scripts as much as possible, using header contribution, instead of pushing all of the logic out in an ajax request. -Heavy javascript widgets (I think you mentioned using YUI controls in an earlier message? Maybe they are taking a long time to run or too much memory?) -User agent memory leaks or "pseudo leaks" which cause performance to degrade over time (especially in IE) MSDN actually has a fairly useful article on IE memory leaks: http://msdn.microsoft.com/en-us/library/bb250448%28VS.85%29.aspx Don't try to fix until you've verified the source of the performance hit. RUSSELL E. MORRISEY Programmer Analyst Professional Mission Solutions Engineering, LLC | [email protected] | www.missionse.com -----Original Message----- From: Jochen Mader [mailto:[email protected]] Sent: Thursday, February 25, 2010 4:48 AM To: [email protected] Subject: Re: Speeding Up HTML Parse??? a) Read the speed tracer output, if the time is spent with the redirect or loading the actual markup it will tell you. b) HTML rendering in the browser is influenced by the markup and ajax. Read the speed tracer output and it will tell you where the time is spent. It's most likely not wicket that costs the initial 30 second delay but some resource taking long to load, an AJAX component doing its magic ... But that's all client(browser)-side stuff. This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
