Re: [zfs-discuss] ZFS write throttling

2008-02-15 Thread Marion Hakanson
[EMAIL PROTECTED] said: > I also tried using O_DSYNC, which stops the pathological behaviour but makes > things pretty slow - I only get a maximum of about 20MBytes/sec, which is > obviously much less than the hardware can sustain. I may misunderstand this situation, but while you're waiting for

Re: [zfs-discuss] ZFS write throttling

2008-02-15 Thread Bob Friesenhahn
On Fri, 15 Feb 2008, Roch Bourbonnais wrote: >> The latter appears to be bug 6429855. But the underlying behaviour >> doesn't really seem desirable; are there plans afoot to do any work on >> ZFS write throttling to address this kind of thing? > > Throttling is being addressed. > > http://bug

Re: [zfs-discuss] ZFS write throttling

2008-02-15 Thread Tao Chen
On 2/15/08, Roch Bourbonnais <[EMAIL PROTECTED]> wrote: > > Le 15 févr. 08 à 11:38, Philip Beevers a écrit : > [...] > > Obviously this isn't good behaviour, but it's particularly unfortunate > > given that this checkpoint is stuff that I don't want to retain in any > > kind of cache anyway - i

Re: [zfs-discuss] ZFS write throttling

2008-02-15 Thread Philip Beevers
Hi Roch, Thanks for the response. > Throttling is being addressed. > > > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6429205 > > > BTW, the new code will adjust write speed to disk speed very quickly. > You will not see those ultra fast initial checkpoints. Is > this a c

Re: [zfs-discuss] ZFS write throttling

2008-02-15 Thread Roch Bourbonnais
Le 15 févr. 08 à 11:38, Philip Beevers a écrit : > Hi everyone, > > This is my first post to zfs-discuss, so be gentle with me :-) > > I've been doing some testing with ZFS - in particular, in > checkpointing > the large, proprietary in-memory database which is a key part of the > application I

[zfs-discuss] ZFS write throttling

2008-02-15 Thread Philip Beevers
Hi everyone, This is my first post to zfs-discuss, so be gentle with me :-) I've been doing some testing with ZFS - in particular, in checkpointing the large, proprietary in-memory database which is a key part of the application I work on. In doing this I've found what seems to be some fairly unh