jabailo@texeme.com wrote:
> I build a system where a Windows service iterates through a file and
> sends each line in the file as a record to a database, by calling a
> web service asynchronously. It runs on a w2k server.
>
> What I notice is:
>
> When the web service gets called, there seems to be a slowness and
> potential for missed calls - my guess is because it's being moved into
> memory. This causes problems as records are dropped. My solution
> is to redo the load if it notices that records are missing.
>
> One thought I had : Is it possible to force the web service to stay
> in memory ( pre-cached, basically ) so that it's /always/ ready to
> serve?

jabailo@texeme.com wrote:
> Giuseppe Nacci wrote:
>> jabailo@texeme.com wrote:
>>
>>> I build a system where a Windows service iterates through a file and
>>> sends each line in the file as a record to a database, by calling a
>>> web service asynchronously. It runs on a w2k server.
>>>
>>> What I notice is:
>>>
>>> When the web service gets called, there seems to be a slowness and
>>> potential for missed calls - my guess is because it's being moved
>>> into memory. This causes problems as records are dropped. My
>>> solution is to redo the load if it notices that records are missing.
>>>
>>> One thought I had : Is it possible to force the web service to stay
>>> in memory ( pre-cached, basically ) so that it's /always/ ready to
>>> serve?
>>
>>
>> Yes, It's possible but you must use ISA Server in cache mode or in
>> integrated mode.
>>
>
> Can I just do this:
>
> [WebMethod]
> (
> Description="mymethod",
> CacheDuration=43200)
> ]
>
> And set it to some incredibly high value ( like 48 hours ) ?

Giuseppe Nacci wrote:
> jabailo@texeme.com wrote:
>
>>I build a system where a Windows service iterates through a file and
>>sends each line in the file as a record to a database, by calling a
>>web service asynchronously. It runs on a w2k server.
>>
>>What I notice is:
>>
>>When the web service gets called, there seems to be a slowness and
>>potential for missed calls - my guess is because it's being moved into
>>memory. This causes problems as records are dropped. My solution
>>is to redo the load if it notices that records are missing.
>>
>>One thought I had : Is it possible to force the web service to stay
>>in memory ( pre-cached, basically ) so that it's /always/ ready to
>>serve?
>
>
> Yes, It's possible but you must use ISA Server in cache mode or in
> integrated mode.
>

Giuseppe Nacci wrote:
> jabailo@texeme.com wrote:
>
>>Giuseppe Nacci wrote:
>>
>>>jabailo@texeme.com wrote:
>>>
>>>
>>>>I build a system where a Windows service iterates through a file and
>>>>sends each line in the file as a record to a database, by calling a
>>>>web service asynchronously. It runs on a w2k server.
>>>>
>>>>What I notice is:
>>>>
>>>>When the web service gets called, there seems to be a slowness and
>>>>potential for missed calls - my guess is because it's being moved
>>>>into memory. This causes problems as records are dropped. My
>>>>solution is to redo the load if it notices that records are missing.
>>>>
>>>>One thought I had : Is it possible to force the web service to stay
>>>>in memory ( pre-cached, basically ) so that it's /always/ ready to
>>>>serve?
>>>
>>>
>>>Yes, It's possible but you must use ISA Server in cache mode or in
>>>integrated mode.
>>>
>>
>>Can I just do this:
>>
>>[WebMethod]
>>(
>> Description="mymethod",
>> CacheDuration=43200)
>>]
>>
>>And set it to some incredibly high value ( like 48 hours ) ?
>
>
> Where? In IE or where do you 'll want to set cache duration?