From owner-freebsd-current Wed Mar 7 6:38:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id DEAEB37B71A; Wed, 7 Mar 2001 06:38:11 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f27EbmR59707; Wed, 7 Mar 2001 16:37:51 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200103071437.f27EbmR59707@gratis.grondar.za> To: Bruce Evans Cc: Maxim Sobolev , dougb@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: harvest_interrupt=YES slows down machine References: In-Reply-To: ; from Bruce Evans "Thu, 08 Mar 2001 00:42:39 +1100." Date: Wed, 07 Mar 2001 16:38:40 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just do something that causes a lot of interrupts that go through the > random harvester. E.g.: > > dd if=/dev/ad0 of=/dev/null > > causes 7750 interrupts/sec here (on a Celeron 366 overclocked to > 522). The random task takes 100% of the available cpu cycles. This > slows down cpu-bound processes by a factor of about 3.5. With a block > size of 64k instead of the default of 512, this causes only 300 > interrupts/sec. The random task takes a measly 27% of the cpu to > process these. It can apparently only handle about 10 interrupts/second > with a reasonable overhead (1%). OK. Try tweaking the "Computational intensity factor" ;-) by dropping the kern.random.yarrow.bins: # sysctl -w kern.random.yarrow.bins=2 And let me know how well that works. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message