I developed a ASMX web service with empty boday (return immediately). The
API has a few parameters, all .Net objects. The client application is a
simple WCF client keep calling this ASMX web service API.
I am measuring the performance of ASMX. What I found is that the first a few
thousand calls are all getting through quickly as I expected. Then the call
was blocked by IIS or ASP.Net because my break point does not get hit for a
few seconds. The calls thereafter were all delayed by something. Now every
call takes second to execute. Sometime, if I pause on my breakpoint for a
few seconds, then remove the break point, the calls after that will get
through quickly. After a few thousand calls, the same problem occurred
again.
I thought the problem is triggerred by some sort of buffering, but could not
find any real clue.
Hao

Hi Hao,

Regarding on the ASP.NET webservice responding issue under thousands
method calls, I think you can try using a normal .net 2.0 webservice client
to perform the same test and check the behavior. If the problem is caused
by server-side ASMX service, a normal .net 2.0 service proxy should also be
able to repro it. Also, would you provide the code snippet in your client
application which execute thousands of webmethod calls?

In addition, I'm wondering whether this is a specific behavior occuring at
debugging time. You can set server-side service's <compilation debug="true"
/> and test it again(printout webmethod execute timespan) to see whether
the problem still occurs.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================

Hi Hao,

How are you doing on this issue, have you got any progress? If there is
still anything we can help, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

It seems as an issue specific to a single PC. My guess is that some third
party web service tracing tool caused the problem, even after I tried to
remove these tools.
Not a big concern to me since it is not a common issue on other machines.
Thanks.
Hao

[quoted text, click to view]

Thanks for your followup Hao,

Well, if you meet new problem or anything we can help, please feel free to
post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead