2009SP1 Webservices slow response on first request

kfuglsang
Member Posts: 26
Hi all,
I have been developing a test solution based on the 2009 SP1 webservices. My findings are, however, that the first request to the webservices takes about 5 seconds to get a response no matter the response size. Any subsequent request is finished relatively quickly (means reasonably, what I would expect).
The webservices is requested through a .net application. If I let an amount of time, say 20 minutes, pass it will take 5 seconds to do the first request again.
Regarding this, I think it would be very interesting to know if anyone else has experienced this?
Any ideas to how I can avoid this "initialization time"?
I have been developing a test solution based on the 2009 SP1 webservices. My findings are, however, that the first request to the webservices takes about 5 seconds to get a response no matter the response size. Any subsequent request is finished relatively quickly (means reasonably, what I would expect).
The webservices is requested through a .net application. If I let an amount of time, say 20 minutes, pass it will take 5 seconds to do the first request again.
Regarding this, I think it would be very interesting to know if anyone else has experienced this?
Any ideas to how I can avoid this "initialization time"?
0
Comments
-
I know this behavior from IIS applications, where the worker process is killed after given time (I think that 20 minutes is default). It looks same for WCF. But I do not know how to set this in WCF... (similar problem like e.g. there: http://www.netframeworkdev.com/windows- ... 3818.shtml)0
-
Sounds correct yes.
I will check tomorrow if I can find a way to tweak the recycling settings for the NAV webservices, although I have a feeling they might be hidden pretty well0 -
As workaround you can use some scheduler to run some call for the webservice in given period to just keep the webservice "warm".0
-
The webservice will reuse a previously used connection if another request for the same user comes in within a given time period (in 2009 SP1). As far as I remember this period is set to 10 seconds.
The main reason for reusing the connection is that the database connection then does not need to be re-established.
Hope this helps.Best regards,
Jens Møller-Pedersen [MSFT]
This posting is provided 'AS IS' with no warranties, and confers no rights.0 -
Unfortunately it doesnt really help.
The application isn't much loaded given the nature of it, so each user will get the experience that it opens very slowly.
I have created a small vb-script to query the webservice every 10 minutes, but to be honest I hope another solution will appear.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions