|
|
You're in the
dotnet web services
group:Invoking Web Service from WinForm App VERY slow first call
dotnet web services:
We have been putting together a Win Forms application that consumes a web service to obtain item information for a client. We've found that the first call to the web service from the application, no matter what the call is, takes way, way too long. We've timed it at over 15 seconds, but the second call from within the same app takes 4-500 milliseconds. We've found a couple of references to things that might decrease the initial time, but nothing definite. Anyone have suggestions on handling this? The classes handling the web service calls were written in VB.NET using 3.5 framework and using Web Services references rather than Service References. Using VS 2008. Thanks,
I had a similar problem with .NET Remoting in the past. This may or may not
be the same issue for you. In our case the remote object was loading a lot of data as it was initialized. It turns out that with .NET Remoting the remote object is not actually created until the client application invokes a method or property. So the client program would start up and create the proxy and you think everything is great. Then when a user tried to invoke it they had to wait for intitialization. It was really a matter of understanding the lifetime of a remote object and getting the architecture correct. I would start by looking at the initialization code and finding out if that is the slow down. [quoted text, click to view] "Jim Owen" wrote:
> Hi, > We have been putting together a Win Forms application that consumes a web > service to obtain item information for a client. We've found that the first > call to the web service from the application, no matter what the call is, > takes way, way too long. We've timed it at over 15 seconds, but the second > call from within the same app takes 4-500 milliseconds. > > We've found a couple of references to things that might decrease the initial > time, but nothing definite. > > Anyone have suggestions on handling this? The classes handling the web > service calls were written in VB.NET using 3.5 framework and using Web > Services references rather than Service References. Using VS 2008. > > Thanks, >
Thanks for the reply.
We've narrowed it down to something that is occurring on our client side but have not totally sorted it out. It appears that there is significant overhead when it is first invoked, but what is generated appears to be cached for some period after generation. To test this, we wrote a small console app that simply invokes the web service through a class then prints out the elapsed time on the console. When the exe is first executed, the entire process requires 15 - 18 seconds. Executing the same executable a second time cuts the elapsed time to 3-4 seconds. Executing again produces the same results. However, if you wait 10 minutes or so and execute the program again, elapsed time again shoots up to 15-18 seconds. There's obviously initialization going on behind the scene that we're not seeing. We'd like to eliminate that init when first called or at least minimize it. Thanks, Jim [quoted text, click to view] "Jeff" wrote:
> I had a similar problem with .NET Remoting in the past. This may or may not > be the same issue for you. In our case the remote object was loading a lot of > data as it was initialized. It turns out that with .NET Remoting the remote > object is not actually created until the client application invokes a method > or property. So the client program would start up and create the proxy and > you think everything is great. Then when a user tried to invoke it they had > to wait for intitialization. It was really a matter of understanding the > lifetime of a remote object and getting the architecture correct. > > I would start by looking at the initialization code and finding out if that > is the slow down. > > "Jim Owen" wrote: > > > Hi, > > We have been putting together a Win Forms application that consumes a web > > service to obtain item information for a client. We've found that the first > > call to the web service from the application, no matter what the call is, > > takes way, way too long. We've timed it at over 15 seconds, but the second > > call from within the same app takes 4-500 milliseconds. > > > > We've found a couple of references to things that might decrease the initial > > time, but nothing definite. > > > > Anyone have suggestions on handling this? The classes handling the web > > service calls were written in VB.NET using 3.5 framework and using Web > > Services references rather than Service References. Using VS 2008. > > > > Thanks, > >
[quoted text, click to view]
On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: > Thanks for the reply. > > We've narrowed it down to something that is occurring on our client side but > have not totally sorted it out. It appears that there is significant > overhead when it is first invoked, but what is generated appears to be cached > for some period after generation. > > To test this, we wrote a small console app that simply invokes the web > service through a class then prints out the elapsed time on the console. > When the exe is first executed, the entire process requires 15 - 18 seconds. > Executing the same executable a second time cuts the elapsed time to 3-4 > seconds. Executing again produces the same results. However, if you wait 10 > minutes or so and execute the program again, elapsed time again shoots up to > 15-18 seconds. > > There's obviously initialization going on behind the scene that we're not > seeing. We'd like to eliminate that init when first called or at least > minimize it. > > Thanks, > Jim > > "Jeff" wrote: > > I had a similar problem with .NET Remoting in the past. This may or may not > > be the same issue for you. In our case the remote object was loading a lot of > > data as it was initialized. It turns out that with .NET Remoting the remote > > object is not actually created until the client application invokes a method > > or property. So the client program would start up and create the proxy and > > you think everything is great. Then when a user tried to invoke it they had > > to wait for intitialization. It was really a matter of understanding the > > lifetime of a remote object and getting the architecture correct. > > > I would start by looking at the initialization code and finding out if that > > is the slow down. > > > "Jim Owen" wrote: > > > > Hi, > > > We have been putting together a Win Forms application that consumes a web > > > service to obtain item information for a client. We've found that the first > > > call to the web service from the application, no matter what the call is, > > > takes way, way too long. We've timed it at over 15 seconds, but the second > > > call from within the same app takes 4-500 milliseconds. > > > > We've found a couple of references to things that might decrease the initial > > > time, but nothing definite. > > > > Anyone have suggestions on handling this? The classes handling the web > > > service calls were written in VB.NET using 3.5 framework and using Web > > > Services references rather than Service References. Using VS 2008. > > > > Thanks, > > > > Jim it's not the server rebuilding is it? IIS isn't shutting down and restarting? you could recycle the app pool and see if it gives the same lag after the recycle. you could also try invoking the same web service from another app on
As far as we can tell, no. This is a remote service with dozens of users
invoking services continually. There does not appear to be issues with other clients. (We have three different development locations, each with the same issue, so it does not appear to be network or connection related.) We have not yet found the exact cause, but we're looking into the initialization process. Jim [quoted text, click to view] "densial" wrote:
> On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: > > Thanks for the reply. > > > > We've narrowed it down to something that is occurring on our client side but > > have not totally sorted it out. It appears that there is significant > > overhead when it is first invoked, but what is generated appears to be cached > > for some period after generation. > > > > To test this, we wrote a small console app that simply invokes the web > > service through a class then prints out the elapsed time on the console. > > When the exe is first executed, the entire process requires 15 - 18 seconds. > > Executing the same executable a second time cuts the elapsed time to 3-4 > > seconds. Executing again produces the same results. However, if you wait 10 > > minutes or so and execute the program again, elapsed time again shoots up to > > 15-18 seconds. > > > > There's obviously initialization going on behind the scene that we're not > > seeing. We'd like to eliminate that init when first called or at least > > minimize it. > > > > Thanks, > > Jim > > > > "Jeff" wrote: > > > I had a similar problem with .NET Remoting in the past. This may or may not > > > be the same issue for you. In our case the remote object was loading a lot of > > > data as it was initialized. It turns out that with .NET Remoting the remote > > > object is not actually created until the client application invokes a method > > > or property. So the client program would start up and create the proxy and > > > you think everything is great. Then when a user tried to invoke it they had > > > to wait for intitialization. It was really a matter of understanding the > > > lifetime of a remote object and getting the architecture correct. > > > > > I would start by looking at the initialization code and finding out if that > > > is the slow down. > > > > > "Jim Owen" wrote: > > > > > > Hi, > > > > We have been putting together a Win Forms application that consumes a web > > > > service to obtain item information for a client. We've found that the first > > > > call to the web service from the application, no matter what the call is, > > > > takes way, way too long. We've timed it at over 15 seconds, but the second > > > > call from within the same app takes 4-500 milliseconds. > > > > > > We've found a couple of references to things that might decrease the initial > > > > time, but nothing definite. > > > > > > Anyone have suggestions on handling this? The classes handling the web > > > > service calls were written in VB.NET using 3.5 framework and using Web > > > > Services references rather than Service References. Using VS 2008. > > > > > > Thanks, > > > > > > Jim > > it's not the server rebuilding is it? IIS isn't shutting down and > restarting? you could recycle the app pool and see if it gives the > same lag after the recycle. > > you could also try invoking the same web service from another app on > another machine, see what that does.
[quoted text, click to view] "Jim Owen" <jimo@online.nospam> wrote in message news:25550D86-9CB8-4EFF-944F-6F47D55687E6@microsoft.com... > As far as we can tell, no. This is a remote service with dozens of users > invoking services continually. There does not appear to be issues with > other > clients. (We have three different development locations, each with the > same > issue, so it does not appear to be network or connection related.) > > We have not yet found the exact cause, but we're looking into the > initialization process. > > Jim > > "densial" wrote: > >> On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: >> > Thanks for the reply. >> > >> > We've narrowed it down to something that is occurring on our client >> > side but >> > have not totally sorted it out. It appears that there is significant >> > overhead when it is first invoked, but what is generated appears to be >> > cached >> > for some period after generation. >> > >> > To test this, we wrote a small console app that simply invokes the web >> > service through a class then prints out the elapsed time on the >> > console. >> > When the exe is first executed, the entire process requires 15 - 18 >> > seconds. >> > Executing the same executable a second time cuts the elapsed time to >> > 3-4 >> > seconds. Executing again produces the same results. However, if you >> > wait 10 >> > minutes or so and execute the program again, elapsed time again shoots >> > up to >> > 15-18 seconds. >> > >> > There's obviously initialization going on behind the scene that we're >> > not >> > seeing. We'd like to eliminate that init when first called or at least >> > minimize it. >> > >> > Thanks, >> > Jim >> > >> > "Jeff" wrote: >> > > I had a similar problem with .NET Remoting in the past. This may or >> > > may not >> > > be the same issue for you. In our case the remote object was loading >> > > a lot of >> > > data as it was initialized. It turns out that with .NET Remoting the >> > > remote >> > > object is not actually created until the client application invokes a >> > > method >> > > or property. So the client program would start up and create the >> > > proxy and >> > > you think everything is great. Then when a user tried to invoke it >> > > they had >> > > to wait for intitialization. It was really a matter of understanding >> > > the >> > > lifetime of a remote object and getting the architecture correct. >> > >> > > I would start by looking at the initialization code and finding out >> > > if that >> > > is the slow down. >> > >> > > "Jim Owen" wrote: >> > >> > > > Hi, >> > > > We have been putting together a Win Forms application that consumes >> > > > a web >> > > > service to obtain item information for a client. We've found that >> > > > the first >> > > > call to the web service from the application, no matter what the >> > > > call is, >> > > > takes way, way too long. We've timed it at over 15 seconds, but >> > > > the second >> > > > call from within the same app takes 4-500 milliseconds. >> > >> > > > We've found a couple of references to things that might decrease >> > > > the initial >> > > > time, but nothing definite. >> > >> > > > Anyone have suggestions on handling this? The classes handling the >> > > > web >> > > > service calls were written in VB.NET using 3.5 framework and using >> > > > Web >> > > > Services references rather than Service References. Using VS 2008. >> > >> > > > Thanks, >> > >> > > > Jim >> >> it's not the server rebuilding is it? IIS isn't shutting down and >> restarting? you could recycle the app pool and see if it gives the >> same lag after the recycle. >> >> you could also try invoking the same web service from another app on >> another machine, see what that does. >> This sounds like the serialization assemblies being created at runtime. Try changing the settings of the Serialization Assembly dropdown at the bottom of the Build pane of the properties window for the project. -- -------------------------------------------------------------------------------- John Saunders | MVP – Windows Server System – Connected System Developer
That looks like it handled the initial slows!
Thanks John - much appreciated. - Jim [quoted text, click to view] "John Saunders [MVP]" wrote:
> > > "Jim Owen" <jimo@online.nospam> wrote in message > news:25550D86-9CB8-4EFF-944F-6F47D55687E6@microsoft.com... > > As far as we can tell, no. This is a remote service with dozens of users > > invoking services continually. There does not appear to be issues with > > other > > clients. (We have three different development locations, each with the > > same > > issue, so it does not appear to be network or connection related.) > > > > We have not yet found the exact cause, but we're looking into the > > initialization process. > > > > Jim > > > > "densial" wrote: > > > >> On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: > >> > Thanks for the reply. > >> > > >> > We've narrowed it down to something that is occurring on our client > >> > side but > >> > have not totally sorted it out. It appears that there is significant > >> > overhead when it is first invoked, but what is generated appears to be > >> > cached > >> > for some period after generation. > >> > > >> > To test this, we wrote a small console app that simply invokes the web > >> > service through a class then prints out the elapsed time on the > >> > console. > >> > When the exe is first executed, the entire process requires 15 - 18 > >> > seconds. > >> > Executing the same executable a second time cuts the elapsed time to > >> > 3-4 > >> > seconds. Executing again produces the same results. However, if you > >> > wait 10 > >> > minutes or so and execute the program again, elapsed time again shoots > >> > up to > >> > 15-18 seconds. > >> > > >> > There's obviously initialization going on behind the scene that we're > >> > not > >> > seeing. We'd like to eliminate that init when first called or at least > >> > minimize it. > >> > > >> > Thanks, > >> > Jim > >> > > >> > "Jeff" wrote: > >> > > I had a similar problem with .NET Remoting in the past. This may or > >> > > may not > >> > > be the same issue for you. In our case the remote object was loading > >> > > a lot of > >> > > data as it was initialized. It turns out that with .NET Remoting the > >> > > remote > >> > > object is not actually created until the client application invokes a > >> > > method > >> > > or property. So the client program would start up and create the > >> > > proxy and > >> > > you think everything is great. Then when a user tried to invoke it > >> > > they had > >> > > to wait for intitialization. It was really a matter of understanding > >> > > the > >> > > lifetime of a remote object and getting the architecture correct. > >> > > >> > > I would start by looking at the initialization code and finding out > >> > > if that > >> > > is the slow down. > >> > > >> > > "Jim Owen" wrote: > >> > > >> > > > Hi, > >> > > > We have been putting together a Win Forms application that consumes > >> > > > a web > >> > > > service to obtain item information for a client. We've found that > >> > > > the first > >> > > > call to the web service from the application, no matter what the > >> > > > call is, > >> > > > takes way, way too long. We've timed it at over 15 seconds, but > >> > > > the second > >> > > > call from within the same app takes 4-500 milliseconds. > >> > > >> > > > We've found a couple of references to things that might decrease > >> > > > the initial > >> > > > time, but nothing definite. > >> > > >> > > > Anyone have suggestions on handling this? The classes handling the > >> > > > web > >> > > > service calls were written in VB.NET using 3.5 framework and using > >> > > > Web > >> > > > Services references rather than Service References. Using VS 2008. > >> > > >> > > > Thanks, > >> > > >> > > > Jim > >> > >> it's not the server rebuilding is it? IIS isn't shutting down and > >> restarting? you could recycle the app pool and see if it gives the > >> same lag after the recycle. > >> > >> you could also try invoking the same web service from another app on > >> another machine, see what that does. > >> > > This sounds like the serialization assemblies being created at runtime. Try > changing the settings of the Serialization Assembly dropdown at the bottom > of the Build pane of the properties window for the project. > -- > -------------------------------------------------------------------------------- > John Saunders | MVP – Windows Server System – Connected System Developer > >
I have a similar problem with visual studio 2008. I didn't find that
'changing the settings of the Serialization Assembly' helped. What did improve the edit performance which was horrendous was turning off auto completion but it is still slower than VStudio 2005. However the Build is very very slow. -- Victor [quoted text, click to view] "Jim Owen" wrote:
> That looks like it handled the initial slows! > Thanks John - much appreciated. > > - Jim > > "John Saunders [MVP]" wrote: > > > > > > > "Jim Owen" <jimo@online.nospam> wrote in message > > news:25550D86-9CB8-4EFF-944F-6F47D55687E6@microsoft.com... > > > As far as we can tell, no. This is a remote service with dozens of users > > > invoking services continually. There does not appear to be issues with > > > other > > > clients. (We have three different development locations, each with the > > > same > > > issue, so it does not appear to be network or connection related.) > > > > > > We have not yet found the exact cause, but we're looking into the > > > initialization process. > > > > > > Jim > > > > > > "densial" wrote: > > > > > >> On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: > > >> > Thanks for the reply. > > >> > > > >> > We've narrowed it down to something that is occurring on our client > > >> > side but > > >> > have not totally sorted it out. It appears that there is significant > > >> > overhead when it is first invoked, but what is generated appears to be > > >> > cached > > >> > for some period after generation. > > >> > > > >> > To test this, we wrote a small console app that simply invokes the web > > >> > service through a class then prints out the elapsed time on the > > >> > console. > > >> > When the exe is first executed, the entire process requires 15 - 18 > > >> > seconds. > > >> > Executing the same executable a second time cuts the elapsed time to > > >> > 3-4 > > >> > seconds. Executing again produces the same results. However, if you > > >> > wait 10 > > >> > minutes or so and execute the program again, elapsed time again shoots > > >> > up to > > >> > 15-18 seconds. > > >> > > > >> > There's obviously initialization going on behind the scene that we're > > >> > not > > >> > seeing. We'd like to eliminate that init when first called or at least > > >> > minimize it. > > >> > > > >> > Thanks, > > >> > Jim > > >> > > > >> > "Jeff" wrote: > > >> > > I had a similar problem with .NET Remoting in the past. This may or > > >> > > may not > > >> > > be the same issue for you. In our case the remote object was loading > > >> > > a lot of > > >> > > data as it was initialized. It turns out that with .NET Remoting the > > >> > > remote > > >> > > object is not actually created until the client application invokes a > > >> > > method > > >> > > or property. So the client program would start up and create the > > >> > > proxy and > > >> > > you think everything is great. Then when a user tried to invoke it > > >> > > they had > > >> > > to wait for intitialization. It was really a matter of understanding > > >> > > the > > >> > > lifetime of a remote object and getting the architecture correct. > > >> > > > >> > > I would start by looking at the initialization code and finding out > > >> > > if that > > >> > > is the slow down. > > >> > > > >> > > "Jim Owen" wrote: > > >> > > > >> > > > Hi, > > >> > > > We have been putting together a Win Forms application that consumes > > >> > > > a web > > >> > > > service to obtain item information for a client. We've found that > > >> > > > the first > > >> > > > call to the web service from the application, no matter what the > > >> > > > call is, > > >> > > > takes way, way too long. We've timed it at over 15 seconds, but > > >> > > > the second > > >> > > > call from within the same app takes 4-500 milliseconds. > > >> > > > >> > > > We've found a couple of references to things that might decrease > > >> > > > the initial > > >> > > > time, but nothing definite. > > >> > > > >> > > > Anyone have suggestions on handling this? The classes handling the > > >> > > > web > > >> > > > service calls were written in VB.NET using 3.5 framework and using > > >> > > > Web > > >> > > > Services references rather than Service References. Using VS 2008. > > >> > > > >> > > > Thanks, > > >> > > > >> > > > Jim > > >> > > >> it's not the server rebuilding is it? IIS isn't shutting down and > > >> restarting? you could recycle the app pool and see if it gives the > > >> same lag after the recycle. > > >> > > >> you could also try invoking the same web service from another app on > > >> another machine, see what that does. > > >> > > > > This sounds like the serialization assemblies being created at runtime. Try > > changing the settings of the Serialization Assembly dropdown at the bottom > > of the Build pane of the properties window for the project. > > -- > > -------------------------------------------------------------------------------- > > John Saunders | MVP – Windows Server System – Connected System Developer > > > >
hello i have also this problem, its worst than you think it keeps me 27s waiting. I have a pda application calling the webservice on II6.0 using also VS 2005 on vb, I have already two servers deployed on this the same situation. I also try the application pool settings but my web maintenance did improve on turning off the shutdown worker process after being idle for 20 mins. Hmmm i read about webservice compression but i guess this is a way far behind the issue on first call. I also thought on doing an upgrade to asp.net 3.5 and vs 2008 but i guess the problem still there i've been looking this issues for almost 4months already and find no good solution hope that microsoft team could address this. Thanks
Hi John,
Hopefully this post will find its way back to you - or perhaps be answered by someone else. As I mentioned in my last post on the earlier portion of this thread, changing the serialization settings for the build handled the initial slows we encountered when invoking the web service. Since that time, we ported the original VB.net code over to C# - this was done to make it cleaner easier to include the project in the rest of the C# solution. The problem is that the initial slows have re-appeared despite ensuring the serialization option in the project were set to "On" and trying every combination that we could think of. We're using VS2008 Team Suite with the 3.5 framework. The web references are still defined as web references rather that service references. Any ideas what this might be at this time? Regards, Jim [quoted text, click to view] "John Saunders [MVP]" wrote:
> > > "Jim Owen" <jimo@online.nospam> wrote in message > news:25550D86-9CB8-4EFF-944F-6F47D55687E6@microsoft.com... > > As far as we can tell, no. This is a remote service with dozens of users > > invoking services continually. There does not appear to be issues with > > other > > clients. (We have three different development locations, each with the > > same > > issue, so it does not appear to be network or connection related.) > > > > We have not yet found the exact cause, but we're looking into the > > initialization process. > > > > Jim > > > > "densial" wrote: > > > >> On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: > >> > Thanks for the reply. > >> > > >> > We've narrowed it down to something that is occurring on our client > >> > side but > >> > have not totally sorted it out. It appears that there is significant > >> > overhead when it is first invoked, but what is generated appears to be > >> > cached > >> > for some period after generation. > >> > > >> > To test this, we wrote a small console app that simply invokes the web > >> > service through a class then prints out the elapsed time on the > >> > console. > >> > When the exe is first executed, the entire process requires 15 - 18 > >> > seconds. > >> > Executing the same executable a second time cuts the elapsed time to > >> > 3-4 > >> > seconds. Executing again produces the same results. However, if you > >> > wait 10 > >> > minutes or so and execute the program again, elapsed time again shoots > >> > up to > >> > 15-18 seconds. > >> > > >> > There's obviously initialization going on behind the scene that we're > >> > not > >> > seeing. We'd like to eliminate that init when first called or at least > >> > minimize it. > >> > > >> > Thanks, > >> > Jim > >> > > >> > "Jeff" wrote: > >> > > I had a similar problem with .NET Remoting in the past. This may or > >> > > may not > >> > > be the same issue for you. In our case the remote object was loading > >> > > a lot of > >> > > data as it was initialized. It turns out that with .NET Remoting the > >> > > remote > >> > > object is not actually created until the client application invokes a > >> > > method > >> > > or property. So the client program would start up and create the > >> > > proxy and > >> > > you think everything is great. Then when a user tried to invoke it > >> > > they had > >> > > to wait for intitialization. It was really a matter of understanding > >> > > the > >> > > lifetime of a remote object and getting the architecture correct. > >> > > >> > > I would start by looking at the initialization code and finding out > >> > > if that > >> > > is the slow down. > >> > > >> > > "Jim Owen" wrote: > >> > > >> > > > Hi, > >> > > > We have been putting together a Win Forms application that consumes > >> > > > a web > >> > > > service to obtain item information for a client. We've found that > >> > > > the first > >> > > > call to the web service from the application, no matter what the > >> > > > call is, > >> > > > takes way, way too long. We've timed it at over 15 seconds, but > >> > > > the second > >> > > > call from within the same app takes 4-500 milliseconds. > >> > > >> > > > We've found a couple of references to things that might decrease > >> > > > the initial > >> > > > time, but nothing definite. > >> > > >> > > > Anyone have suggestions on handling this? The classes handling the > >> > > > web > >> > > > service calls were written in VB.NET using 3.5 framework and using > >> > > > Web > >> > > > Services references rather than Service References. Using VS 2008. > >> > > >> > > > Thanks, > >> > > >> > > > Jim > >> > >> it's not the server rebuilding is it? IIS isn't shutting down and > >> restarting? you could recycle the app pool and see if it gives the > >> same lag after the recycle. > >> > >> you could also try invoking the same web service from another app on > >> another machine, see what that does. > >> > > This sounds like the serialization assemblies being created at runtime. Try > changing the settings of the Serialization Assembly dropdown at the bottom > of the Build pane of the properties window for the project. > -- > -------------------------------------------------------------------------------- > John Saunders | MVP – Windows Server System – Connected System Developer > >
[quoted text, click to view]
On May 4, 4:14=A0pm, Jim Owen <j...@online.nospam> wrote: > Hi John, > > =A0 Hopefully this post will find its way back to you - or perhaps be answ= ered > by someone else. =A0As I mentioned in my last post on the earlier portion = of > this thread, changing the serialization settings for the build handled the= > initial slows we encountered when invoking the web service. > > =A0 Since that time, we ported the original VB.net code over to C# - this = was > done to make it cleaner easier to include the project in the rest of the C= # > solution. > > =A0 The problem is that the initial slows have re-appeared despite ensurin= g > the serialization option in the project were set to "On" and trying every > combination that we could think of. > > =A0 We're using VS2008 Team Suite with the 3.5 framework. =A0 =A0The web > references are still defined as web references rather that service referen= ces. > > =A0 Any ideas what this might be at this time? > > =A0 Regards, > > =A0 Jim > > > > "John Saunders [MVP]" wrote: > > > "Jim Owen" <j...@online.nospam> wrote in message > >news:25550D86-9CB8-4EFF-944F-6F47D55687E6@microsoft.com... > > > As far as we can tell, no. =A0This is a remote service with dozens of = users > > > invoking services continually. =A0There does not appear to be issues w= ith > > > other > > > clients. =A0(We have three different development locations, each with = the > > > same > > > issue, so it does not appear to be network or connection related.) > > > > We have not yet found the exact cause, but we're looking into the > > > initialization process. > > > > Jim > > > > "densial" wrote: > > > >> On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: > > >> > Thanks for the reply. > > > >> > We've narrowed it down to something that is occurring on our client= > > >> > side but > > >> > have not totally sorted it out. =A0It appears that there is signifi= cant > > >> > overhead when it is first invoked, but what is generated appears to= be > > >> > cached > > >> > for some period after generation. > > > >> > To test this, we wrote a small console app that simply invokes the = web > > >> > service through a class then prints out the elapsed time on the > > >> > console. > > >> > When the exe is first executed, the entire process requires 15 - 18= > > >> > seconds. > > >> > Executing the same executable a second time cuts the elapsed time t= o > > >> > 3-4 > > >> > seconds. =A0Executing again produces the same results. =A0However, = if you > > >> > wait 10 > > >> > minutes or so and execute the program again, elapsed time again sho= ots > > >> > up to > > >> > 15-18 seconds. > > > >> > There's obviously initialization going on behind the scene that we'= re > > >> > not > > >> > seeing. =A0We'd like to eliminate that init when first called or at= least > > >> > minimize it. > > > >> > Thanks, > > >> > Jim > > > >> > "Jeff" wrote: > > >> > > I had a similar problem with .NET Remoting in the past. This may = or > > >> > > may not > > >> > > be the same issue for you. In our case the remote object was load= ing > > >> > > a lot of > > >> > > data as it was initialized. It turns out that with .NET Remoting = the > > >> > > remote > > >> > > object is not actually created until the client application invok= es a > > >> > > method > > >> > > or property. So the client program would start up and create the > > >> > > proxy and > > >> > > you think everything is great. Then when a user tried to invoke i= t > > >> > > they had > > >> > > to wait for intitialization. It was really a matter of understand= ing > > >> > > the > > >> > > lifetime of a remote object and getting the architecture correct.= > > > >> > > I would start by looking at the initialization code and finding o= ut > > >> > > if that > > >> > > is the slow down. > > > >> > > "Jim Owen" wrote: > > > >> > > > Hi, > > >> > > > We have been putting together a Win Forms application that cons= umes > > >> > > > a web > > >> > > > service to obtain item information for a client. We've found th= at > > >> > > > the first > > >> > > > call to the web service from the application, no matter what th= e > > >> > > > call is, > > >> > > > takes way, way too long. =A0We've timed it at over 15 seconds, = but > > >> > > > the second > > >> > > > call from within the same app takes 4-500 milliseconds. > > > >> > > > We've found a couple of references to things that might decreas= e > > >> > > > the initial > > >> > > > time, but nothing definite. > > > >> > > > Anyone have suggestions on handling this? =A0The classes handli= ng the > > >> > > > web > > >> > > > service calls were written in VB.NET using 3.5 framework and us= ing > > >> > > > Web > > >> > > > Services references rather than Service References. =A0Using VS= 2008. > > > >> > > > Thanks, > > > >> > > > Jim > > > >> it's not the server rebuilding is it? IIS isn't shutting down and > > >> restarting? you could recycle the app pool and see if it gives the > > >> same lag after the recycle. > > > >> you could also try invoking the same web service from another app on > > >> another machine, see what that does. > > > This sounds like the serialization assemblies being created at runtime. = Try > > changing the settings of the Serialization Assembly dropdown at the bott= om > > of the Build pane of the properties window for the project. > > -- > > ------------------------------------------------------------------------= ---=AD----- > > John Saunders | MVP =96 Windows Server System =96 Connected System Devel= oper- Hide quoted text - > > - Show quoted text - I'm having the exact same issue with VS 2008 Team System with C# .net 3.5 XML web services. Changing the Serialization Assembly worked to speed up the development box, but did not help the IIS on 2k3 box. Does anyone have something else to try? Along with this, it seems that giving the app a 3-5 minute break between calls will cause the same thing. The next call will take 15+ seconds to complete when it had been doing them in a half second or less. Is there something to set that can help keep the objects "alive"?
Hi Mike,
We eventually solved the issue although I'm not totally sure exactly what we changed to make it work correctly. In this particular solution, we have about 8 projects, most of which access the web service and do so through a set of wrapper classes in one of the projects. We went though ALL of the projects and ensured that the Generate Serialization Assembly was set to On for all projects. We then rebuilt the entire solution and set the XMLSerialization dll's to read-only access. After doing various repititions of the above, it began working as expected. I suspect that the read-only file attribute was not necessary, but we did get it working. The issue is that the framework will generate the XML serialization assembly for the call to the web service unless it is told to generate them in advance. That compilation eats up the time. Hope this helps, - Jim [quoted text, click to view] "kessler.mike@gmail.com" wrote:
> On May 4, 4:14 pm, Jim Owen <j...@online.nospam> wrote: > > Hi John, > > > > Hopefully this post will find its way back to you - or perhaps be answered > > by someone else. As I mentioned in my last post on the earlier portion of > > this thread, changing the serialization settings for the build handled the > > initial slows we encountered when invoking the web service. > > > > Since that time, we ported the original VB.net code over to C# - this was > > done to make it cleaner easier to include the project in the rest of the C# > > solution. > > > > The problem is that the initial slows have re-appeared despite ensuring > > the serialization option in the project were set to "On" and trying every > > combination that we could think of. > > > > We're using VS2008 Team Suite with the 3.5 framework. The web > > references are still defined as web references rather that service references. > > > > Any ideas what this might be at this time? > > > > Regards, > > > > Jim > > > > > > > > "John Saunders [MVP]" wrote: > > > > > "Jim Owen" <j...@online.nospam> wrote in message > > >news:25550D86-9CB8-4EFF-944F-6F47D55687E6@microsoft.com... > > > > As far as we can tell, no. This is a remote service with dozens of users > > > > invoking services continually. There does not appear to be issues with > > > > other > > > > clients. (We have three different development locations, each with the > > > > same > > > > issue, so it does not appear to be network or connection related.) > > > > > > We have not yet found the exact cause, but we're looking into the > > > > initialization process. > > > > > > Jim > > > > > > "densial" wrote: > > > > > >> On Mar 27, 6:36 am, Jim Owen <j...@online.nospam> wrote: > > > >> > Thanks for the reply. > > > > > >> > We've narrowed it down to something that is occurring on our client > > > >> > side but > > > >> > have not totally sorted it out. It appears that there is significant > > > >> > overhead when it is first invoked, but what is generated appears to be > > > >> > cached > > > >> > for some period after generation. > > > > > >> > To test this, we wrote a small console app that simply invokes the web > > > >> > service through a class then prints out the elapsed time on the > > > >> > console. > > > >> > When the exe is first executed, the entire process requires 15 - 18 > > > >> > seconds. > > > >> > Executing the same executable a second time cuts the elapsed time to > > > >> > 3-4 > > > >> > seconds. Executing again produces the same results. However, if you > > > >> > wait 10 > > > >> > minutes or so and execute the program again, elapsed time again shoots > > > >> > up to > > > >> > 15-18 seconds. > > > > > >> > There's obviously initialization going on behind the scene that we're > > > >> > not > > > >> > seeing. We'd like to eliminate that init when first called or at least > > > >> > minimize it. > > > > > >> > Thanks, > > > >> > Jim > > > > > >> > "Jeff" wrote: > > > >> > > I had a similar problem with .NET Remoting in the past. This may or > > > >> > > may not > > > >> > > be the same issue for you. In our case the remote object was loading > > > >> > > a lot of > > > >> > > data as it was initialized. It turns out that with .NET Remoting the > > > >> > > remote > > > >> > > object is not actually created until the client application invokes a > > > >> > > method > > > >> > > or property. So the client program would start up and create the > > > >> > > proxy and > > > >> > > you think everything is great. Then when a user tried to invoke it > > > >> > > they had > > > >> > > to wait for intitialization. It was really a matter of understanding > > > >> > > the > > > >> > > lifetime of a remote object and getting the architecture correct. > > > > > >> > > I would start by looking at the initialization code and finding out > > > >> > > if that > > > >> > > is the slow down. > > > > > >> > > "Jim Owen" wrote: > > > > > >> > > > Hi, > > > >> > > > We have been putting together a Win Forms application that consumes > > > >> > > > a web > > > >> > > > service to obtain item information for a client. We've found that > > > >> > > > the first > > > >> > > > call to the web service from the application, no matter what the > > > >> > > > call is, > > > >> > > > takes way, way too long. We've timed it at over 15 seconds, but > > > >> > > > the second > > > >> > > > call from within the same app takes 4-500 milliseconds. > > > > > >> > > > We've found a couple of references to things that might decrease > > > >> > > > the initial > > > >> > > > time, but nothing definite. > > > > > >> > > > Anyone have suggestions on handling this? The classes handling the > > > >> > > > web > > > >> > > > service calls were written in VB.NET using 3.5 framework and using > > > >> > > > Web > > > >> > > > Services references rather than Service References. Using VS 2008. > > > > > >> > > > Thanks, > > > > > >> > > > Jim > > > > > >> it's not the server rebuilding is it? IIS isn't shutting down and > > > >> restarting? you could recycle the app pool and see if it gives the > > > >> same lag after the recycle. > > > > > >> you could also try invoking the same web service from another app on > > > >> another machine, see what that does. > > > > > This sounds like the serialization assemblies being created at runtime. Try > > > changing the settings of the Serialization Assembly dropdown at the bottom > > > of the Build pane of the properties window for the project. > > > -- > > > ---------------------------------------------------------------------------Â----- > > > John Saunders | MVP – Windows Server System – Connected System Developer- Hide quoted text - > > > > - Show quoted text - > > > I'm having the exact same issue with VS 2008 Team System with C# .net > 3.5 XML web services.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |