Date: Fri, 22 Jan 2016 00:05:26 -0500 From: Mason Loring Bliss <mason@blisses.org> To: "Michael B. Eichorn" <ike@michaeleichorn.com> Cc: dweimer <dweimer@dweimer.net>, freebsd-questions@freebsd.org Subject: Re: ZFS performance help sought Message-ID: <20160122050526.GO4538@blisses.org> In-Reply-To: <1453438096.26786.7.camel@michaeleichorn.com> References: <20160121205139.GG4538@blisses.org> <ea3f05f9a8c20bd62a1c391b432dafe2@dweimer.net> <20160121232810.GJ4538@blisses.org> <20160121235545.GK4538@blisses.org> <20160122000523.GL4538@blisses.org> <1453438096.26786.7.camel@michaeleichorn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 21, 2016 at 11:48:16PM -0500, Michael B. Eichorn wrote: > freebsd.org/doc/en_US.ISO8859-1/books/handbook/zfs-advanced.html Hm. I don't know that I've looked at this before. Thank you. I'll read it. > I suppose vfs.zfs.top_maxinflight might worth a try? Sure. Does it have any correspondence with the qlen iostat -x reports? I don't know how many levels have queueing, and whether iostat is reading the drive's tagged command queueing, something in the filesystem, or something elsewhere in the kernel. I'll try to figure this out tomorrow, as well as reading the rest of that page and testing with top_maxinflight. If iostat is reporting something else, is there a good way to capture current inflight to see how close to the cap I'm getting in any event? -- Mason Loring Bliss mason@blisses.org http://blisses.org/ "I am a brother of jackals, and a companion of ostriches." (Job 30 : 29)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160122050526.GO4538>