I would like to caution people about this conventional
wisdom. For UFS the I/O size tunable like maxphys ended up
as an important parameter to the write throttle algorithm.
The bigger it was the less coupled the application would be
to the storage and some important gains could come from
that.
Sa
On 4/25/06, Eric C. Saxe <[EMAIL PROTECTED]> wrote:
> Do you have the bug# around for these problems?
6417367 cpu_wakeup() could be more locality/CMT aware
4933914 scheduler support for shared cache CMT processors
Thank you.
Holger
___
perf-discuss
Hi
Could someone please comment on:
1. Disk usage after a default install (build >30) in MB (ex studio and src)
2. Memory footprint (X not started ie command-line logon...build >30) in MB
Thank you
PS: I only have builds < 30 ...
This message posted from opensolaris.org
___
