简单Web服务上的代码分析 [英] Code Profiling On Simple Web service

问题描述

现有应用程序提供接近12秒的响应时间。使用VSTS 2008进行代码分析表明，Web应用程序对Web服务的调用时间接近3秒。可以在代理对象构造函数上将3秒进一步拆分为2秒。方法调用还有1个。
为了隔离这种行为，我尝试使用asp.net页面来调用Web服务的默认hello world方法。我在本地Web服务器上部署了客户端asp.net appln和asmx服务。完成代码分析后，观察到代理构造函数调用本身接近1.7秒。 （请注意，构造函数中没有代码。这是默认的hello world web服务）

简单地启动webservice调用1.7秒似乎是一个非常高的数字。任何人都可以解释为什么只需要这么长时间来启动对象。这是序列化的成本吗？

谢谢你

An existing application is providing a response time of close to 12 seconds. Code profiling using VSTS 2008 suggests that the call to the webservice from the web application is taking close to 3 seconds. The 3 seconds can be further split into 2 seconds on the proxy object constructor. and additional 1 for the method call.
To isolate this behaviour, i have tried using an asp.net page to call the default hello world method of a web service. I deployed the client asp.net appln and the asmx service on the local web server. When code profiling was done, it was observed that the proxy constructor call itself took close to 1.7 secs. ( Pl. note there is no code in the constructor. This is the default hello world web service)

1.7 secs for simply initiating a webservice call seems to be a very high number. Can anyone throw some light on why is it taking so long to simply initiate the object. Is this the cost of serialization?


Thanks in adv

推荐答案

为什么不分析代码并找出？

Why not profile the code and find out?

这篇关于简单Web服务上的代码分析的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！