From owner-freebsd-questions@FreeBSD.ORG Wed Nov 22 15:30:43 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A57416A50C for ; Wed, 22 Nov 2006 15:30:43 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id F031243D53 for ; Wed, 22 Nov 2006 15:30:11 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Wed, 22 Nov 2006 10:30:40 -0500 id 000564CB.45646D20.00000729 Received: from Internal Mail-Server by mx01 (envelope-from wmoran@collaborativefusion.com) with AES256-SHA encrypted SMTP; 22 Nov 2006 10:30:39 -0500 Date: Wed, 22 Nov 2006 10:30:38 -0500 From: Bill Moran To: VeeJay Message-Id: <20061122103038.758d313c.wmoran@collaborativefusion.com> In-Reply-To: <2cd0a0da0611220715n7e88564ahe19f20d033ed39a9@mail.gmail.com> References: <2cd0a0da0611220715n7e88564ahe19f20d033ed39a9@mail.gmail.com> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.10.6; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Does disk encryption causes a performance penalty for Data Access/Read/Write, etc X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 15:30:43 -0000 In response to VeeJay : > > Does *disk encryption* causes a *performance* penalty for Data > Access/Read/Write, etc? Any kind of encryption causes a performance penalty. However, if your CPU is powerful enough, it's possible (even likely) that the CPU is still able to encrypt faster than the disk can write the data. The result would be that you won't notice the penalty unless you've got other CPU-intensive tasks running that reduce the amount of CPU available to the encryption process. HTH -- Bill Moran Collaborative Fusion Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.