Date: Mon, 22 Aug 2005 13:48:29 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: freebsd-current@freebsd.org, Giorgos Keramidas <keramida@freebsd.org>, Kris Kennaway <kris@obsecurity.org> Subject: Re: [PATCH]: fdalloc optimization Message-ID: <20050822134710.T896@fledge.watson.org> In-Reply-To: <20050822083320.GA32668@stud.fit.vutbr.cz> References: <20050821084546.GA77111@stud.fit.vutbr.cz> <20050821175406.GA36164@xor.obsecurity.org> <20050822074002.GA31176@stud.fit.vutbr.cz> <20050822074932.GA2264@beatrix.daedalusnetworks.priv> <20050822083320.GA32668@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Aug 2005, Divacky Roman wrote:
>> By running an application that opens (and keeps open) many files, i.e.
>> a program that creates many temporary files, keeps them open and then
>> closes them all at once before exiting?
>
> I did:
>
> gettimeofday(&t1, NULL);
> for (; i>0; i--) {
> if (open("/dev/null", O_RDONLY) == -1) {
> perror(NULL);
> break;
> }
> }
> gettimeofday(&t2, NULL);
src/tools/tools/syscall_timing provides a number of simple
micro-benchmarks of common system calls, including several that allocate
file descriptors (such as pipe creation, socket allocation, etc). Run
about ten sets each of {before,after}, drop the first entry for each
("warmup"), and then use ministat to compare the results on a couple of
key system calls?
Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050822134710.T896>
