From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 12 22:26:19 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A1B76FC; Wed, 12 Dec 2012 22:26:19 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99]) by mx1.freebsd.org (Postfix) with ESMTP id 77C138FC0A; Wed, 12 Dec 2012 22:26:18 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id qBCMQGNF001473; Wed, 12 Dec 2012 23:26:16 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id qBCMQGXp001470; Wed, 12 Dec 2012 23:26:16 +0100 (CET) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Wed, 12 Dec 2012 23:26:16 +0100 (CET) From: Wojciech Puchar To: Stefan Esser Subject: Re: FreeBSD for serious performance? In-Reply-To: <50C889D3.1050404@freebsd.org> Message-ID: References: <20121211204323.310760@gmx.com> <50C889D3.1050404@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (wojtek.tensor.gdynia.pl [127.0.0.1]); Wed, 12 Dec 2012 23:26:16 +0100 (CET) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2012 22:26:19 -0000 > The cause of the low write performance is the disabled write cache. > Enabling the write cache is unsafe on SATA drives (with or without > NCQ), since they do not make any guarantees that nearby data is not > lost if power fails during a disk write. It never happened to me, > but there is a reason that SAS drives have less capacity, much lower > BER (one to two magnitudes) and are more expensive than SATA drives. interface have nothing to do. Both allows you to force writes now and then. > The solution to the performance problem is simple: Turn on the write > cache. If the data is valuable, then SAS is the solution to both the If data is valuable, regular and well done backup practice is the only solution. > would pay one developer hour. Asking Nvidia to release the confidential > documentation for their chip-set might help, but I doubt that there is > much interest to add support for NCQ to an obsolete chip-set, today, > unless you pay a developer (and even then ...). Even without this, i've never seen properly working NVidia hardware. ANY