Date: Sun, 11 Nov 2007 00:02:43 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Randall Hyde <randyhyde@earthlink.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Some FreeBSD performance Issues Message-ID: <20071110130243.GU82929@server.vk2pj.dyndns.org> In-Reply-To: <002f01c822ee$b04ac4b0$6302a8c0@pentiv> References: <000701c82253$b3a8c030$6302a8c0@pentiv> <20071108225238.GB22005@dan.emsphone.com> <4734061D.9000606@freebsd.org> <002f01c822ee$b04ac4b0$6302a8c0@pentiv>
next in thread | previous in thread | raw e-mail | index | archive | help
--PyMzGVE0NRonI6bs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 09, 2007 at 08:36:32AM -0800, Randall Hyde wrote: >To answer a different question in the thread, I'm pretty sure I'm making >only one FreeBSD call per byte, at least in one of the cases I posted. How about using ktrace or similar to confirm this. >I wonder if I'm only getting one character output per time slice, or >something like that? Maybe, though I don't understand why this would occur. If you time(1) your program, what are the real/user/system time breakdown? That will help clarify where the slowdown is located. Have you tried the dd(1) command suggested. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an RFC2821-compliant MTA. --PyMzGVE0NRonI6bs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHNavz/opHv/APuIcRAs/uAJ9fYLHzIXo/aqMBodk5qRBqWVFi7gCfbzjn P5eKhofT0J3VNiuHgs9z0Ws= =R6nQ -----END PGP SIGNATURE----- --PyMzGVE0NRonI6bs--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071110130243.GU82929>