From owner-freebsd-hackers Thu Mar 7 0:51: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id E303F37B404 for ; Thu, 7 Mar 2002 00:51:06 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id B11DDAE1D0; Thu, 7 Mar 2002 00:51:06 -0800 (PST) Date: Thu, 7 Mar 2002 00:51:06 -0800 From: Alfred Perlstein To: Dimitar Peikov Cc: freebsd-hackers@freebsd.org Subject: Re: Swapping performance Message-ID: <20020307085106.GB26621@elvis.mu.org> References: <20020307104518.0f73740b.mitko@rila.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020307104518.0f73740b.mitko@rila.bg> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Dimitar Peikov [020307 00:45] wrote: > I start some performance tests on -stable and on SuSE 7.1 / 2.4.17. I > don't comment about 'bzero' performance, but when RAM is over, Linux > is much faster. I have no idea what is the algorithm of swapping but it seems that the granularity of swapping pieces is the key or the importance of swapping memory blocks of certain task. Ooo I forgot to say that the both machines have the same hardware, IBM 300PL, 256 RAM and no other tasks running. I had to run these tests to choose the fastest platform for building our software indexes, which requires a lot of math and memory operations. > > --- with bzero --- > Linux$ time ./malloc_test Could you explain what "malloc_test" actually does and/or share the code? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message