Mittwoch, 14. Oktober 2009 17:44Hi,
One of my WFE server's CPU is constanly running at 100%. It is the W3WP.exe process. It is pointing to the main web aplication app pool. It use IISPeek to see what's going on and here's the main cause it reported back:
REQUEST: 14771806791734011480 VERB: POST URL: /rd/_vti_bin/sitedata.asmx
ELAPSED: 1 PIPE-STATE: Processing TIME-IN-STATE: 0
CLIENT-IP: 10.12.30.250 PORT: 80
Based on the above, it is point to the RD site collection that is causing the CPU spike. The "_vti_bin/sitedata.asmx" is the Sharepoint Web Services. I look at the site, it does not have anything other than the default Announcements, Links, etc. There are, however, a bunch of subsite but this should not cause it as it is point to the RD (top level site) and each subsites would have its own "_vti_bin/sitedata.asmx".
I can stop and restart the process... but it would spike up again after some time. So, how can I figure out what in that site is causing this?
Thanks in advance.
Mittwoch, 14. Oktober 2009 17:55is making a reference to metadata List webservices, have you custom code to call webservices?? how many user are trying to connect to that webservices you have knowledge? this have impact and off course impact on your w3w.exe process, many requests, the more IIS have to process...
André Lage Microsoft SharePoint and CRM Consultant
Mittwoch, 14. Oktober 2009 21:23Thanks for the comment.
This is the top lovel site. There's nothing on that site I see have been customized. The webparts are the default webparts. This is crazy.
Donnerstag, 15. Oktober 2009 19:49
Is this a 32 bit deployment? If yes, can you check boot.ini (usually you can tell notepad to open C:\boot.ini to see it) to see if you have the /3GB switch? If yes, take it out and reboot the server. 32bit SharePoint and /3GB switch don't play nice. See KB933560.
Donnerstag, 15. Oktober 2009 20:23Also are you running in a virtualized environment? If so make sure the clock is synced with the other servers. Another thing to check is the loopback. Are you able to access the site directly from the server?
Aseem Nayar - MSFT
This posting is provided "AS IS" with no warranties, and confers no rights
Donnerstag, 15. Oktober 2009 21:05What are your other WFEs doing when this one is spiking?
I have seen this when load balancing gets out of synch and directs all traffic to a single node. I would also suggest that you temporarily add another worker process to the web app - and see if it still spikes at that capacity.
Freitag, 16. Oktober 2009 04:12Moderator
I think André Lage recommended you to find out how many times the sitedata.asmx was called, that is, the workload of the web service. You may find it out in IIS log, it will record every call to the web services in sitedata.asmx. Just count the number of sitedata.asmx records during a period of time will reveal the workload. And from the c-ip field (http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/ffdd7079-47be-4277-921f-7a3a6e610dcb.mspx?mfr=true ) in IISlog, you can also figure out where these web service calling were from.
And the article follows also shows how to analyze the performance of web services with the IISLog time-taken field: http://blogs.msdn.com/alikl/archive/2007/11/02/identify-asp-net-web-services-and-wcf-performance-issues-by-examining-iis-logs.aspx .
- Als Antwort markiert GuYumingMicrosoft Contingent Staff, Moderator Mittwoch, 21. Oktober 2009 01:45
Mittwoch, 21. Oktober 2009 06:39
Thanks all for the comments. I have opened a ticket with MS Support. As always, they want you to run a bunch of diags etc... still working on it. To answer some of the questions:
- All my servers are physical
- Running 64 bit W2k3 R2 Enterprise
- 6GB RAM
The spike seems to alternate amonth the two WFE servers. Meaning, it doesn't seem like it is specific to one server. However, I do notice in each case, it is telling me that the spike is coming from http://mydomain/rd/_vti_bin/sitedata.asmx. This is why it is leading me to feel is a specific site related.
Dienstag, 3. November 2009 16:09Update... MS Tech tooks some IIS and performance dump. The results incates a large xml file (4MB) was pushing thru the IIS when the CPU spiked. Again, I don't see much in the site that would do something like this. I am waiting to chat with the Tech and see if we can zero it down further.
BTW. I am running W2K3 R3 w/ SP2 x64. Have 12GB RAM on the server w/ Quad Core... all physical servers. When this server peaks, the other WFE is unaffected.
Dienstag, 20. Juli 2010 03:41Did you find a solution for this? I was experiencing the same issue, and like you discovered IISPeek > sitedata.asmx... I soon after tracked it down to my incremental searches.