MOSS 2007 application is quite slow every now and then
Hi, all: I have posted similar thread quite while ago (Moderator: 18th September 2009) and several experts offered really good ref. however, the issue is not resolved totally yet. here I give updates. We have a MOSS sites in production environment, 3 tier arthiceture - 2 WFEs, 1 SQL DB cluster (two DBserver) and 1 CMS server. All supermachine matching MOSS hardware requirement. However, the page is opening quite slow every now and then - it happens once on several days. For instance, user types the site URL from public access, it took over 30secs to 1 min to receive 1st piece of data from server side. Look like the server is preparing something or just idle there before responding. This issue occurs for both CMS and WFEs nodes! We checked MOSS log from all servers and DB logs, even logs, processor/memory usage by performance tool in win 2003.. all seems more or less fine :( Ofc, it is a heavily customized MOSS solution package, implemented many webparts. thus it is so hard to trace the problem since I am not a experienced system&network&MOSS guru. I simply would like to know where or which server introduced the latency and then I can focus on the certain place.. I wonder if there is such a tool that can install on all servers and clients, so that once the client trigger a page request, we can see from all servers how long it took from hop to hop (such as from application server to backend SQL server). Best regards,MyST from Finland :D
February 22nd, 2010 5:55pm

This could happen due to multiple reasons few of them:1. When the Site is not used for sometime, the W3Wp instance of Application pool is stopped, so when users access it for the first time, it takes sometime to invoke the W3wp AND CAUSE A DELAY.2. This could be due to network congestion between the DB and the WFE servers due to some Job like Backup running on the servers.3. Check incase some maintenance job runs automatically on the Backend DB servers causing this.4. Incase the site try to access the data from outside of sharepoint, the souce being slow might cause the delay5. Any Scheduled Task running on the sharepoint boxes causing the issue.further, you can load Httpwatch on your client machine and browse the site when it is coming up slow, this will show each component loading on the page and also the time taken by them, this will help you to Narow down the issue.Also, you might want to enable CACHING on the site if required.Thanks!I LOVE MS..... Thanks and Regards, Kshitiz (Posting is provided "AS IS" with no warranties, and confers no rights.)
Free Windows Admin Tool Kit Click here and download it now
February 22nd, 2010 6:06pm

Hi Using Disposable SharePoint Objects - Several of the Windows SharePoint Services objects, primarily the SPSite class and SPWeb class objects, are created as managed objects. However, these objects use unmanaged code and memory to perform the majority of their work. The managed part of the object is small; the unmanaged part of the object is much larger.- In the SharePoint object model, the SPSite and SPWeb objects are created in managed code as a small wrapper (approximately 2 KB in size). This wrapper then creates unmanaged objects, which can average approximately 1–2 MB in size. If you assume that the SPWeb.Webs collection has 10 subsites, a total of 10 items are created, each with an average of 2 MB of memory (for a total of 20 MB). And Handling exceptions Register the Client-side Script Shared by Multiple Web Parts to Improve Performance 1. If you have multiple Web Parts that share client-side script, you can improve performance and simplify maintenance by placing the script in an external file and registering the script for the page. In this way, the code is cached on the client computer on first use and does not need to be resent to the client for each request. Asynchronous Data Fetching 1. Use an asynchronous thread for any operation that could take a significant amount of time. In particular, if a database or HTTP request is made, an asynchronous fetch allows other parts to continue processing without being blocked. Caching1. Use a Web Part cache to store property values and to expedite data retrieval.Page SizeA relative increase in the page size can have a significant impact on performance if that page is accessed by a large number of people every day, especially during peak hours. Therefore it is suggested to keep code size to a minimum.These are few tips to solve your problem. Hope it will help.
February 22nd, 2010 8:06pm

Hi, there: Thank you two above for comments! To give more updates: From MOSS ULSlog, we found that several DB queries wait a long time (over 15secs) to receive result in the bad performance period. However, those queries are just normal sites and we cannot reproduce the issue after the bad time, meaning all of those queries are running super fast afterwards. We suspect that the DB environment is the most suspecious place to check. We found that: 1. the MOSS DBs log files are backuped each 2 - 4 hrs. I googled this, MS suggested us to do frequent log files backup. 2. DB server system resource is not in a abnormal situation during the period: CPU, system memory, W3WP thread memory all seem fine. We start to think about the DB backend feature, is it because the requested resource from the query had no indexing during that time or some other threads in DB application blocks the queries? it seems not so simple as just a 'bad SQL query ' but involve DB system environment or something else. We will check more. Br, Xi from Finland :D
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2010 1:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics