Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932351AbWAZPbe (ORCPT ); Thu, 26 Jan 2006 10:31:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932364AbWAZPbe (ORCPT ); Thu, 26 Jan 2006 10:31:34 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:59150 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S932351AbWAZPbe (ORCPT ); Thu, 26 Jan 2006 10:31:34 -0500 Date: Thu, 26 Jan 2006 16:33:43 +0100 From: Jens Axboe To: Hans Reiser Cc: Edward Shishkin , LKML , Reiserfs mail-list Subject: Re: random minor benchmark: Re: Copy 20 tarfiles: ext2 vs (reiser4, unixfile) vs (reiser4,cryptcompress) Message-ID: <20060126153343.GH4311@suse.de> References: <43D7C6BE.1010804@namesys.com> <43D7CA7F.4010502@namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D7CA7F.4010502@namesys.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1080 Lines: 40 On Wed, Jan 25 2006, Hans Reiser wrote: > Notice how CPU speed (and number of cpus) completely determines > compression performance. > > cryptcompress refers to the reiser4 compression plugin, (unix file) > refers to the reiser4 non-compressing plugin. > > Edward Shishkin wrote: > > > Here are the tests that vs asked for: > > Creation (dd) of 20 tarfiles (the original 200M file is in ramfs) > > Kernel: 2.6.15-mm4 + current git snapshot of reiser4 > > > > ------------------------------------------ > > > > Laputa workstation > > Uni Intel Pentium 4 (2.26 GHz) 512M RAM > > > > ext2: > > real 2m, 15s > > sys 0m, 14s > > > > reiser4(unix file) > > real 2m, 7s > > sys 0m, 23s > > > > reiser4(cryptcompress, lzo1, 64K) > > real 2m, 13s > > sys 0m, 11s Just curious - does your crypt plugin reside in user space? -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/