From owner-freebsd-performance@FreeBSD.ORG Fri Dec 14 02:44:24 2007 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0D4C16A419 for ; Fri, 14 Dec 2007 02:44:24 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate1.pacific.net.sg (smtpgate1.pacific.net.sg [203.120.90.31]) by mx1.freebsd.org (Postfix) with SMTP id 339E613C506 for ; Fri, 14 Dec 2007 02:44:23 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: (qmail 20366 invoked from network); 14 Dec 2007 02:16:22 -0000 Received: from adsl2.dyn234.pacific.net.sg (HELO P2120.somewherefaraway.com) (oceanare@210.24.234.2) by smtpgate1.pacific.net.sg with ESMTPA; 14 Dec 2007 02:16:21 -0000 Message-ID: <4761E76D.6090202@pacific.net.sg> Date: Fri, 14 Dec 2007 10:16:13 +0800 From: Erich Dollansky User-Agent: Thunderbird 2.0.0.6 (X11/20070826) MIME-Version: 1.0 To: Nash Nipples References: <28761.46997.qm@web36306.mail.mud.yahoo.com> In-Reply-To: <28761.46997.qm@web36306.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-performance@freebsd.org Subject: Re: freebsd vs linux: performance problem X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Dec 2007 02:44:25 -0000 Hi, Nash Nipples wrote: > sounds like a power unit problem. try to switch them and repeat. hey, in the next step you tell him that the MTU is set wrongly. > > > Now, in simple memory access operations, I see the freebsd system being > noticably slower than the linux system. A simple C program that copies As already mentioned, are both systems working as 32 or 64 bit systems? > from one memory buffer to another, when executed in a loop executes > between 10-30% slower on freebsd, as compared to linux. The assembly > code of the program used for testing is identical in both the cases. Don't you call memcpy? Erich