Re: [bug #48169] find makes unnecessary syscalls

[L.A. Walsh]

James Youngman wrote:
> Follow-up Comment #1, bug #48169 (project findutils):
>
> Is there are measurable performance difference?
>   

I don't know about last version, vs. this version, but
a find printing names of all files under
my font dir....

Ishtar:/usr/share/fonts> dropcaches
5.37sec 0.02usr 4.91sys (91.82% cpu)

# w/cold cache for 44k objects:
Ishtar:/usr/share/fonts> time find . -mtime +900000
5.50sec 0.04usr 0.95sys (18.19% cpu)

# w/warm cache: <1s
Ishtar:/usr/share/fonts> time find . |wc
44251   64142 1277265
0.11sec 0.05usr 0.09sys (130.28% cpu)

The following is w/a perl-program using aio:
(1st drop cache again)...
Ishtar:/usr/share/fonts> dropcaches
0.08sec 0.02usr 0.04sys (73.26% cpu)

Ishtar:/usr/share/fonts> time treescan-aio.pl . |wc
44251   64142 1277516
1.03sec 0.19usr 0.04sys (23.35% cpu)

Ishtar:/usr/share/fonts> time treescan-aio.pl . |wc
44251   64142 1277516
0.13sec 0.14usr 0.04sys (137.56% cpu)

I would have thought perl would be slower than
a C program, but find could be seriously improved looking
at the cold-cache case.  Hot-cache case showed more
perl overhead maybe?