Dear All,

i encountered a strange problem.  We have published a large number of
Orchestrations as web services and they are being consumed by different
applications.

It has being discovered that if no call is made to an orchestration (web
service) for some time, the pre-ceding call made gets a poor response time.
Then all calls coming after that call get good response times.

I followed the article on Orhestration Engine Configuration on:
http://msdn2.microsoft.com/en-us/library/aa578610.aspx
and discovered that if i tweak the AppDomain Configuration setting mainly
the <DefaultSpec SecondsIdleBeforeShutdown="1200"
SecondsEmptyBeforeShutdown="1800"> tag to -1, my assemblies will never get
unloaded and thus all requests will have good response times.  Apparantely
the problem is that if for 1200 sec (20mins) the dll does not serve any
request, it gets unloaded.  After this period if it get a requests, it spend
s
most of the time re-loading the dll in memory thus giving a bad response for
that request.

My Question is: Are there any effects of changing this setting, will the
server come under memory constraints if i set it to -1 ?

Has anyone done this and achieved the desired result ?

Any help/advice will be greatly appreicated.
Thanks
Noel Charles

[ Post a follow-up to this message ]