Windows SP 2.6.0

[Young, Darren]

>
>> 
>> Do modern Windows servers impose RAM caps on services or anything like
>>that? Thrashing might explain it.
>> 
>
>There are liable to still be some advanced scheduling capabilities in
>there somewhere (I want to tune my windows box the way I used to OS360),
>but they tend to be turned off.
>
>I would be inclined to watch the start in resmon and see where the cycles
>(or memory, or disk) is going.  Another thing to check would be that this
>is the 32 bit Shibd running, although that us less likely to impact...

Ran procmon during startup and watched what it was doing during startup.

During startup working size grows to around 311MB and when I see the
"applying metadata filter (Signature)² entry in the logs CPU on the server
(8 cores) goes up to around 25% usage. Memory seems to stay around 300MB
then drops to about half that size after it¹s running.

The only thing I see in procmon while it¹s ³spinning² are thread
create/exit operations.

I have the procmon csv output if you want it.


At this point I think I¹ll disable the check of the backup file and see
what that does. Does that require just removing the Signature
MetadataFilter line from the config?