True, the writes took a steep performance hit while the queries were not
as impacted.

This must be it.

'Wish the cache strategy change was logged somewhere.


This email message is for the sole use of the intended recipient(s) and
may contain GDC4S confidential or privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited. If
you are not an intended recipient, please contact the sender by reply
email and destroy all copies of the original message.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Bertram Dorn
Sent: Thursday, November 08, 2007 3:30 PM
To: Lion, Oren-P64304
Cc: Timothy Butler; [email protected]
Subject: Re: [perf-discuss] Could pegged UPS result in performance drop

HI,

i would also guess it is the cache strategy which gets change.

easy to test: you should not see performance impact on random reads.

cu
BUD


Lion, Oren-P64304 wrote:
> Haven't seen anything like that in the docs and the alarms/events do 
> not indicate caching changes.
> 
> 
> This email message is for the sole use of the intended recipient(s) 
> and may contain GDC4S confidential or privileged information. Any 
> unauthorized review, use, disclosure or distribution is prohibited. If

> you are not an intended recipient, please contact the sender by reply 
> email and destroy all copies of the original message.
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Timothy 
> Butler
> Sent: Thursday, November 08, 2007 2:08 PM
> To: [email protected]
> Subject: Re: [perf-discuss] Could pegged UPS result in performance 
> drop
> 
> Does it sense UPS availability and disable write-caching?
>  
>  
> This message posted from opensolaris.org 
> _______________________________________________
> perf-discuss mailing list
> [email protected]
> _______________________________________________
> perf-discuss mailing list
> [email protected]

_______________________________________________
perf-discuss mailing list
[email protected]

Reply via email to