From: antispam@fricas.org   
      
   bart  wrote:   
   > On 30/10/2025 10:15, David Brown wrote:   
   >> On 30/10/2025 01:36, bart wrote:   
   >   
   >>> So, what exactly did I do wrong here (for A68G):   
   >>>   
   >>>    root@DESKTOP-11:/mnt/c/a68g/algol68g-3.10.5# time make >output   
   >>>    real    1m32.205s   
   >>>    user    0m40.813s   
   >>>    sys     0m7.269s   
   >>>   
   >>> This 90 seconds is the actual time I had to hang about waiting. I'd be   
   >>> interested in how I managed to manipulate those figures!   
   >>   
   >> Try "time make -j" as a simple step.   
   >   
   >   
   > OK, "make -j" gave a real time of 30s, about three times faster. (Not   
   > quite sure how that works, given that my machine has only two cores.)   
   >   
   > However, I don't view "-j", and parallelisation, as a solution to slow   
   > compilation. It is just a workaround, something you do when you've   
   > exhausted other possibilities.   
   >   
   > You have to get raw compilation fast enough first.   
      
   >   
   > Quite a few people have suggested that there is something amiss about my   
   > 1:32 and 0:49 timings. One has even said there is something wrong with   
   > my machine.   
      
   Yes, I wrote this.  90 seconds in itself could be OK, your machine   
   just could be slow.  But the numbers you gave clearly show that   
   that only about 50% of time on _one_ core is used to do the build.   
   So something is slowing down your machine.  And this is specific to   
   your setup, as other people running build on Linux get better than   
   90% CPU utilization.  You apparently get offended by this statement.   
   If you are realy interested if fast tools you should investigate   
   what is causing this.   
      
   Anyway, there could be a lot of different reasons for slowdown.   
   Fact that you get 3 times faster build using 'make -j' suggests   
   that some other program is competing for CPU and using more jobs   
   allows getting higher share of CPU.  If that affects only programs   
   running under WSL, than your numbers may or may not be relevant to   
   WSL experience, but are incomparable to Linux timings.  If slowdown   
   affects all programs on your machine, then you should be interested   
   in eliminating it, because it would also make your compiler faster.   
   But that is your machine, if you not curious what happens that   
   is OK.   
      
   --   
                                 Waldek Hebisch   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)