Bob Evans writes:
> One last tidbit, for what it is worth. Rather than watch top, I ran
> xcpustate. It seems that just as the writes pause, the cpu looks like
> it hits 100% (or very close), then it falls back down to its lower
> level.
>
> I'm still getting used to Solaris 10 as well, so if you have a DTrace
> script you'd recommend me running, please feel free to suggest it.
>
>
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I had overlooked that this could be a single CPU system.
For such a test the potential limiting factors can be either
of:
1. storage.
2. the single cp thread burning a CPU.
3. total system CPU overload.
You've already indicated that storage is not 100% busy.
The cp(1) thread is not burning a CPU.
And it looks like the system is not CPU saturated, right ?
I'd argue that the conjunction of those 3 things somewhat
points to 'a problem'.
-r
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
