Date: Wed, 31 Mar 2004 00:21:02 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Dag-Erling Sm?rgrav <des@des.no> Cc: current@freebsd.org Subject: Re: performance of jailed processes Message-ID: <20040330222102.GK8930@darkness.comp.waw.pl> In-Reply-To: <xzpy8piqbkc.fsf@dwp.des.no> References: <Pine.NEB.3.96L.1040330155837.93169O-100000@fledge.watson.org> <xzpy8piqbkc.fsf@dwp.des.no>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Mar 30, 2004 at 11:17:39PM +0200, Dag-Erling Sm?rgrav wrote: +> Robert Watson <rwatson@freebsd.org> writes: +> > On Tue, 30 Mar 2004, Dag-Erling Sm?rgrav 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 -command -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 -command -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. Could you try chroot to / ? By doing: # jail / test <YOUR_IP> `which zsh` # <your test> ? -- Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAafLOForvXbEpPzQRAiZ9AKD2q8J/u3RmLjI7JkDxTCE2QZzhqwCgptXF D7std9sFCBCo/VOVVMk/7fc= =16Wn -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040330222102.GK8930>