From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 10:46:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 626EA16A4CE; Wed, 28 Jan 2004 10:46:07 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0876843D1F; Wed, 28 Jan 2004 10:46:05 -0800 (PST) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 28 Jan 2004 13:46:03 -0500 Message-ID: From: Don Bowman To: 'Robert Watson' , Don Bowman Date: Wed, 28 Jan 2004 13:46:02 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: "'freebsd-current@freebsd.org'" Subject: RE: system call performance 4.x vs 5.x [and UP vs MP] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 18:46:07 -0000 > From: Robert Watson [mailto:rwatson@freebsd.org] > On Wed, 28 Jan 2004, Don Bowman wrote: > ... > > BTW, is your table below "4.7 UP vs 5.x MP"? I was left > unclear from the > title. Generally, the results I see suggest 5.x UP is > currently slower > than 4.x UP (something we should make back up over the next > three or four > months), but that 5.x MP is quite a bit faster than 4.x MP in many > interesting cases (i.e., network throughput, builds, etc). Especially > with the recent IPI changes and scheduling changes, I see > substantially > lower latency in scheduling various kernel threads on 5.x-MP > compared to > 4.x-MP, which means a lot more work gets done. Sorry, its MP versus MP, both on the same box. [i shouldn't have included the UP vs MP in the title, it confuses things, it was just an observation on 4.7 in isolation]. Thank you for the excellent answer. I will try the pipe() suggestion, and the netperf_socket branch. We are definitely seeing that e.g. bridging performance on 5.2 (MP) is very much worse than on 4.7 (MP). --don