Re: [PATCH] add option --no-cache-file and configuration variable no_cache_file

[Shigio Yamaguchi]

Hi,
> As a result of comparing execution time, it turns out that it is applied only
> when perl is configured so that vfork might be used.
> It is faster to use cache file, when using fork.
> 
> Though regrettable, in perl-5.8, vfork is not used any longer. 
> usevfork is disregarded and fork is always used.
> Is there any workaround except using old perl?

I think there is no way except for asking perl people to use vfork.
But there might be some reasons for it.

Originally, a suitable way for UNIX is to make a lot of small processes
using interprocess communication. Using process memory cache means a big
process which needs a lot of time to copy.

If we cannot use vfork(2) then we should select one of the following strategy:

(1) a small process which fork a lot of processes.
(2) a big process which fork lesser processes.

Since we have made a decision adding more processes in anchor'load(),
we had better select (1).
--
Shigio Yamaguchi <address@hidden> - Tama Communications Corporation
Spare mail address: <address@hidden>
PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3