> On Sun, 01 Oct 2006 16:31:30 +0400
> Alex Smirnov <[EMAIL PROTECTED]> wrote:
>
>> Felipe Monteiro de Carvalho ?????:
>> > How do you know it spends more then 99% of compilation time in this
>> > search}
>> >
>> > Also consider that showing output on the screen costs time, and
>> > without showing messages the search will be shorter.
>> >
>> The answer is very simple. My project compilation log file consists
>> of 31491 lines of text. And the number of the lines with "not found"
>> string is 23286. The number of lines with "found" string is 383.
>
> I think, this discussion is missing some numbers. Here are some:
>
> On a normal linux system the compiler searches 55 directories.
> Compiling one simple LCL application with -vewnhi:
> Time: 1.225s
> Not found: 29071
>
> With 55 additional paths in the fpc unit directory:
> Time: 1.493s
> Not found: 55699
>
> With 1000 additional paths in the fpc unit directory:
> Time: 5.843s
> Not found: 520639
>
> This gives about 4.8ms per additional unit path.
> So, the search overhead for the 55 standard paths costs about 0.27s or
> about 22%.
I will add some directory caching in the compiler. That should at least
reduce the number of system calls. I created a mantis issue 7515
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives