Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262945AbVDAWwA (ORCPT ); Fri, 1 Apr 2005 17:52:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262946AbVDAWwA (ORCPT ); Fri, 1 Apr 2005 17:52:00 -0500 Received: from fmr24.intel.com ([143.183.121.16]:3994 "EHLO scsfmr004.sc.intel.com") by vger.kernel.org with ESMTP id S262945AbVDAWvi (ORCPT ); Fri, 1 Apr 2005 17:51:38 -0500 Message-Id: <200504012251.j31MpUg03810@unix-os.sc.intel.com> From: "Chen, Kenneth W" To: "'Linus Torvalds'" Cc: "'Andrew Morton'" , Subject: RE: Industry db benchmark result on recent 2.6 kernels Date: Fri, 1 Apr 2005 14:51:30 -0800 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcU0uyq9M+SRbZwMT8KjJkO2VfZEaACUFhEw In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1154 Lines: 25 Linus Torvalds wrote on Tuesday, March 29, 2005 4:00 PM > Also, it would be absolutely wonderful to see a finer granularity (which > would likely also answer the stability question of the numbers). If you > can do this with the daily snapshots, that would be great. If it's not > easily automatable, or if a run takes a long time, maybe every other or > every third day would be possible? > > Doing just release kernels means that there will be a two-month lag > between telling developers that something pissed up performance. Doing it > every day (or at least a couple of times a week) will be much more > interesting. Indeed, we agree that regular disciplined performance testing is important and we (as Intel) will take on the challenge to support the Linux community. I just got an approval to start this project. We will report more detail on how/where to publish the performance number, etc. - Ken - 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/