From owner-freebsd-current@FreeBSD.ORG Tue Mar 30 13:17:47 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 04F6B16A4CE; Tue, 30 Mar 2004 13:17:47 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC20143D2D; Tue, 30 Mar 2004 13:17:46 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id B775B5309; Tue, 30 Mar 2004 23:17:45 +0200 (CEST) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id DC0DF5308; Tue, 30 Mar 2004 23:17:39 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 2602) id 845E533CAA; Tue, 30 Mar 2004 23:17:39 +0200 (CEST) To: Robert Watson References: From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Tue, 30 Mar 2004 23:17:39 +0200 In-Reply-To: (Robert Watson's message of "Tue, 30 Mar 2004 16:00:03 -0500 (EST)") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63 cc: current@freebsd.org Subject: Re: performance of jailed processes 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: Tue, 30 Mar 2004 21:17:47 -0000 Robert Watson writes: > On Tue, 30 Mar 2004, Dag-Erling Sm=F8rgrav wrote: > > although the query only returns one row, it's a pretty big row, so 13 > > seconds could be explained by per-syscall or per-packet overhead. > Theory goes that there should be no per-read/write system call change in > behavior for TCP with jail. Jail impacts bind/connect, and potentially > each I/O on UDP for an unbound socket using sendto. root@outside /# /usr/bin/time -- sh -c 'echo "my sql query;" | mysql -comma= nd -line -arguments >/dev/null' 0.06 real 0.00 user 0.03 sys root@outside /# jexec 55 zsh root@inside /# /usr/bin/time -- sh -c 'echo "my sql query;" | mysql -comman= d -line -arguments >/dev/null' 13.65 real 0.01 user 0.04 sys so it's definitely not CPU overhead - more likely a scheduling problem. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no