Date: Mon, 12 Nov 2007 17:06:45 +0900 From: "Adrian Chadd" <adrian@freebsd.org> To: "Randall Hyde" <randyhyde@earthlink.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Some FreeBSD performance Issues Message-ID: <d763ac660711120006p6e9749e9rf634bf2a00f22fdd@mail.gmail.com> In-Reply-To: <002701c8248b$9c2b8110$6302a8c0@pentiv> References: <000701c82253$b3a8c030$6302a8c0@pentiv> <20071108225238.GB22005@dan.emsphone.com> <4734061D.9000606@freebsd.org> <002701c8248b$9c2b8110$6302a8c0@pentiv>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/11/2007, Randall Hyde <randyhyde@earthlink.net> wrote: > At this point I'm not sure why FreeBSD's API call is so slow (btw, it's not > the system call that's responsible, if I make several additional API calls > on each read, e.g., doing lseeks, this has only a marginal impact on > performance). But it's pretty clear that if I expect reasonable performance > in my own library I'm going to have to do the same thing that glib does and > switch over to buffered I/O. Pain in the butt, but there's nothing else to > do at this point. Why give up at this point? Why not actually do some pmcstat profiling to see where all the CPU time is going? Adrian -- Adrian Chadd - adrian@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660711120006p6e9749e9rf634bf2a00f22fdd>