Duh!.
Long sync (which delays the next sync) are also possible on
a write intensive workloads. Throttling heavy writters, I
think, is the key to fixing this.
Robert Milkowski writes:
> Hello Roch,
>
> Monday, February 12, 2007, 3:19:23 PM, you wrote:
>
> RP> Robert Milkowski writes:
> >> bash-3.00# dtrace -n fbt::txg_quiesce:return'{printf("%Y
> ",walltimestamp);}'
> >> dtrace: description 'fbt::txg_quiesce:return' matched 1 probe
> >> CPU ID FUNCTION:NAME
> >> 3 38168 txg_quiesce:return 2007 Feb 12 14:08:15
> >> 0 38168 txg_quiesce:return 2007 Feb 12 14:12:14
> >> 3 38168 txg_quiesce:return 2007 Feb 12 14:15:05
> >> ^C
> >>
> >>
> >>
> >> Why I do not see it exactly every 5s?
> >> On other server I get output exactly every 5s.
> >>
> >>
>
> RP> I am not sure about this specific funtion but if the
> RP> question is the same as why is the pool synching more often
> RP> than 5sec, then that can be because of low memory condition
> RP> (if we have too much dirty memory to sync we don't wait the
> RP> 5 seconds.). See arc_tempreserve_space around (ERESTART).
>
> The opposite - why it's not syncing every 5s and rather every
> few minutes on that server.
>
>
> --
> Best regards,
> Robert mailto:[EMAIL PROTECTED]
> http://milek.blogspot.com
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
