Date: Mon, 30 Mar 2015 10:57:41 -0500 From: Mark Felder <feld@FreeBSD.org> To: freebsd-fs@freebsd.org Subject: Re: Little research how rm -rf and tar kill server Message-ID: <1427731061.306961.247099633.0A421E90@webmail.messagingengine.com> In-Reply-To: <5519716F.6060007@artem.ru> References: <55170D9C.1070107@artem.ru> <1427727936.293597.247070269.5CE0D411@webmail.messagingengine.com> <55196FC7.8090107@artem.ru> <1427730597.303984.247097389.165D5AAB@webmail.messagingengine.com> <5519716F.6060007@artem.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 30, 2015, at 10:53, Artem Kuchin wrote: > > This is normal state, not under rm -rf > Do you need it during rm -rf ? > No, but I wonder if changing the timer from LAPIC to HPET or possibly one of the other timers makes the system more responsive under that load. Would you mind testing that? You can switch the timer like this: sysctl kern.eventtimer.timer=HPET And then run some of your I/O tests The full list of available timers is under sysctl kern.eventtimer.choice -- you could try any of them, but the higher the number next to the name is the higher perceived "quality" of the timer by the system. Note this doesn't survive a reboot, but could be set in /etc/sysctl.conf or /boot/loader.conf
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1427731061.306961.247099633.0A421E90>