Michael
Mon Jul 31 04:54:54 CDT 2006
Yes and no. The symptom remains the same, no matter what I try. Every 30
minutes a call to the web application takes between 10 and 15 seconds,
sometimes about 60 seconds . However, one benefit of the test program is
that I don't face the delay in the web client anymore (or let's say most of
the time). Instead it occurs in the test program, running in the background.
Once that happened, both the test app and the web client are back to their
normal speed. I'm thinking about creating a small application running in the
systray or a windows service, so if the delay occurs, there's a fair chance
that the user isn't affected by it.
--
Michael
http://www.stunnware.com/crm2
----------------------------------------------------------
"Daniel Tan" <kenghua@NOSPAMbiz-process.com> schrieb im Newsbeitrag
news:eZGYuoHtGHA.4264@TK2MSFTNGP04.phx.gbl...
> So, any updates?
>
> "Michael Höhne" <michael.hoehne@nospam.nospam> wrote in message
> news:e18F1LZsGHA.3684@TK2MSFTNGP05.phx.gbl...
>> Yes, it's megabyte. If the value isn't set, IIS will use up to half of
>> the available memory. I'm also playing with these number (currently using
>> 1024MB for the cache) and also try to see if setting
>> ObjectCacheTTL=0xffffffff makes any changes. Both options define the
>> caching of static content, not the dynamic content, so I'm not sure that
>> it makes a big difference.
>>
>> I'm currently running tests using a small program opening
>>
http://crmserver//Workplace/home_activities.aspx every minute from the
>> client. This is the activity homepage you see after starting the CRM web
>> client (if the default hasn't been changed). I have two servers, one is
>> the development machine, one the production system, and I'm runing the
>> test on both machines.
>>
>> The current result is:
>>
>> Development system: response time is 140ms most of the time. However,
>> every 30 minutes (very close to it), it takes about 15 seconds to
>> complete. After that, response is back to 140ms.
>> Production system: response time is between 77ms and 202ms. Every 60
>> minutes (again very close), it takes about 10 seconds to complete. Again,
>> response is very fast afterwards.
>>
>> I now have made the following modifications to the development system
>> (Beside the two registry settings mentioned above)
>>
>> Deactivated the option "Shutdown worker processes after being idle for
>> (time in minutes)" on the application pool root.
>> Web garden: changed from 1 to 2 worker processes.
>> MSCRMServices directory: changed the session timeout from 20 to 240.
>>
>> Not sure if any of that changes the behavior, but if it does, I'm posting
>> it here.
>>
>> --
>> Michael
>>
>>
http://www.stunnware.com/crm2
>>
>> ----------------------------------------------------------
>>
>> "Dan Quinton" <DanQuinton@discussions.microsoft.com> schrieb im
>> Newsbeitrag news:7821E9BB-5DD8-4A3C-BF89-66B328F6CCB3@microsoft.com...
>>> In decimal yes. But I believe the value represents Mb of physical
>>> memory, so
>>> unless you have 5,000,000 Mb of RAM I think it should be set lower =)
>>> Unless
>>> Nathan has found it's not Mb but possibly Kb? (5000Mb still sounds high
>>> though.) I presume setting it high just means it has no cap on the
>>> memory it
>>> can allocate.
>>>
>>> Thanks
>>> Dan
>>>
>>> "Ilya Milshtein" wrote:
>>>
>>>> The Value = 5000000 is in decimal base... am I right?
>>>> --
>>>> ----------------------
>>>> regards,
>>>> Ilya Milshtein
>>>>
>>>>
>>>>
>>>>
>>>> "Daniel Tan" wrote:
>>>>
>>>> > Hi Nathan,
>>>> >
>>>> > Thanks for sharing!
>>>> >
>>>> > Gonna give it a try in my VPC.
>>>> >
>>>> >
>>>> > "Nathan Warner" <NathanWarner@discussions.microsoft.com> wrote in
>>>> > message
>>>> > news:6E194410-B9E7-4BE4-9E78-6B75CCFE0770@microsoft.com...
>>>> > > Hi all,
>>>> > >
>>>> > > I thought I would share our finding.
>>>> > >
>>>> > > By increasing the size of the IIS cache you can gain massive
>>>> > > improvement
>>>> > > in
>>>> > > the CRM load time. Due to the massive improvements we have got, we
>>>> > > are in
>>>> > > the process of implementing at all of our client sites.
>>>> > >
>>>> > > To do this you will need to add a registry entry into the following
>>>> > > location:
>>>> > > HKEY_Local_Machine\System\CurrentControlSet\Services\InetInfo\Parameters
>>>> > > Type: DWORD
>>>> > > Name: MemCacheSize
>>>> > > Value: 5000000
>>>> > >
>>>> > > I hope this helps anyone with this issue.
>>>> > >
>>>> > > Regards,
>>>> > > Nathan Warner
>>>> >
>>>> >
>>>> >
>>
>>
>
>