Front page | perl.perl5.porters |
Postings from February 2014
On 4 February 2014 15:34, bulk88 via RT <perlbug-followup@perl.org> wrote:
> On Mon Feb 03 19:02:17 2014, tonyc wrote:
>>
>> This made a significant difference, I did 3 runs for a baseline, with
>> build durations of 718, 735 and 727 seconds[1].
>>
>> I added -DPERL_DISABLE_PMC to the $(MINICORE_OBJ) build command and
>> did another three runs with durations of 643, 698 and 675 seconds.
>>
>> Taking the median of each that's a 7% reduction in build time.
>>
>> Tony
>>
>> [1] this was on my normal desktop, which didn't have a lot of CPU
>> usage, but I guess there was a lot of noise anyway.
>
> Since this ticket is heading down different directions. I'll point the following 3 ideas in this ticket so far.
>
> 1. disabling pmc in miniperl can be done for all OSes, there is also the PERL_IS_MINIPERL macro, so no need to -D it
>
> 2. ${^WIN32_SLOPPY_STAT} for Win32 miniperl only
>
> 3. /lib first on Win32 miniperl only
>
> The reason I/O is slow on the machine I used is probably a combination of 2 things.
Is there any chance it could also be that you have a virus scanner
running on your perl build dir?
I seem to recall that when I worked under windows the security types
at work insisted all directories were under virus scanner, so building
perl became nightmarishly slow as the virus scanner rescanned every
source file during the build.
Just a thought.
Yves
Thread Previous
|
Thread Next