Date: Mon, 21 Nov 2011 22:25:36 +0100 From: Stefan Bethke <stb@lassitu.de> To: Adam Vande More <amvandemore@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Limiting disk I/O by jail or uid? Message-ID: <6354F6F2-959D-4451-A434-32C5C7335C25@lassitu.de> In-Reply-To: <33122B07-5473-4C84-A89D-B4C2F9677BC0@lassitu.de> References: <E04BD92A-EFEA-4EB4-BC57-1F07EC040383@lassitu.de> <CA%2BtpaK3J1BCvGLsNZ_LBuYs9ve08UJY=12HH9Ch%2Bb=3wRbqKNg@mail.gmail.com> <CA545615-4337-439F-A8A5-AD7C2B54BC97@lassitu.de> <CA%2BtpaK1utojFPbvCvwQELgyMi2nno6RMc7dCK_3=b_%2Bp24Yy_w@mail.gmail.com> <33122B07-5473-4C84-A89D-B4C2F9677BC0@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 21.11.2011 um 21:42 schrieb Stefan Bethke: > Am 21.11.2011 um 21:40 schrieb Adam Vande More: >=20 >> On Mon, Nov 21, 2011 at 1:58 PM, Stefan Bethke <stb@lassitu.de> = wrote: >>=20 >> Interesting, but it doesn't seem to offer limiting the I/O bandwidth = induced by a process or jail, or assigning different priorities, which = would need to be implemented in the ZFS or GEOM schedulers, I suppose. >>=20 >> Limiting CPU has long been the poor man's IO scheduler, and has = usually worked pretty well for me but has required some trial and error. = YMMV=20 >=20 > Good point, I'll give that a try. Unfortunately, the process I want to limit is not sufficiently CPU bound = to be limited that way vs. all the other processes. I guess I'll put in = a second disk. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6354F6F2-959D-4451-A434-32C5C7335C25>