Date: Mon, 30 Mar 2015 19:04:26 +0300 From: Artem Kuchin <artem@artem.ru> To: freebsd-fs@freebsd.org Subject: Re: Little research how rm -rf and tar kill server Message-ID: <5519740A.1070902@artem.ru> In-Reply-To: <1427731061.306961.247099633.0A421E90@webmail.messagingengine.com> 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> <1427731061.306961.247099633.0A421E90@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
30.03.2015 18:57, Mark Felder пишет: > > 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 > I see. I will test at night, when load goes down. I cannot say sure that's a right way to dig, but i will test anything :) Just to remind: untar overloads the system, but untar + sync every 120s does not. That seems very strange to me. I think the problem might be somewhere here. Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5519740A.1070902>