Re: slow execution of built executables on a Mac

OK. I've posted a bug: https://ghc.haskell.org/trac/ghc/ticket/15891 Thanks much for the attempts thus far! Richard > On Nov 11, 2018, at 8:13 AM, George Colpitts > wrote: > > I couldn't duplicate this, when system times were high they were

Re: slow execution of built executables on a Mac

I couldn't duplicate this, when system times were high they were usually between 20-40% which seems high but not 80%. I am on Xcode 10.1, macOS 10.13.6 , a 4 core imac with 12 gb RAM and a hard drive not SSDs. I can't go to Mojave as it is an old iMac. I did make -j5 using ghc 8.6.2. The Mac

Re: slow execution of built executables on a Mac

Richard Eisenberg writes: > OK. Well, I couldn't sample from Activity Monitor, because the > processes came and went too quickly. But the terminal command `sample` > takes a *name* as an argument, and so passing ghc-stage1 worked > nicely. Samples were taken during rts_dist_HC calls. > Hmmm, it

Re: slow execution of built executables on a Mac

OK. Well, I couldn't sample from Activity Monitor, because the processes came and went too quickly. But the terminal command `sample` takes a *name* as an argument, and so passing ghc-stage1 worked nicely. Samples were taken during rts_dist_HC calls. Here's the first bit: Call graph: 880

Re: slow execution of built executables on a Mac

Ben, yeah, good point, probabilistically speaking, a few stack traces are often all you need to pinpoint an egregious performance problem, at least that's been my experience. Richard, as you probably know, you can get stack traces by using the Activity Monitor, select a ghc process and choose

Re: slow execution of built executables on a Mac

Richard Eisenberg writes: > Sadly, none of the suggestions on this thread worked. > > But here is some more detail: > > - During stage-1, my machine's CPU is maxed out (or nearly so) in user mode. > - After stage-1 (most obviously during rts_dist_HC), my machine spends > roughly 80% of its CPU

Re: slow execution of built executables on a Mac

Sadly, none of the suggestions on this thread worked. But here is some more detail: - During stage-1, my machine's CPU is maxed out (or nearly so) in user mode. - After stage-1 (most obviously during rts_dist_HC), my machine spends roughly 80% of its CPU in *system* mode. - Testing on my other

Re: slow execution of built executables on a Mac

Maybe a symptom of an AFPS bug? https://gregoryszorc.com/blog/2018/10/29/global-kernel-locks-in-apfs/ Just came across this, might be worth a look. Cheers, Gabor On 10/26/18, Richard Eisenberg wrote: > Hi devs, > > I have a shiny, new iMac in my office. It's thus frustrating that it takes

Re: slow execution of built executables on a Mac

rts_dist_HC is where it builds the various versions of the RTS, right? I noticed a similar slowness building the RTS at ICFP on my MacBook Pro (macOS 10.12). I don't think my battery lasted long enough to get to stage 2. I'm afraid I don't have any clue why it's gotten so slow, but you're not

Re: slow execution of built executables on a Mac

> On Oct 26, 2018, at 5:02 PM, Carter Schonwald > wrote: > > are you setting the intree gmp flag? and/or dont have gmp the library > installed? maybe your ghc is using integer simple! Intriguing possibility. I haven't done anything to install gmp. I'm now at home, away from this machine,

Re: slow execution of built executables on a Mac

theory one: are you setting the intree gmp flag? and/or dont have gmp the library installed? maybe your ghc is using integer simple! theory two: dont set -j greater than about 8 or perhaps 16? (some parts of ghc are slower on too paralle a setup?) those are my two off the cuff guesses you

slow execution of built executables on a Mac

Hi devs, I have a shiny, new iMac in my office. It's thus frustrating that it takes my iMac longer to build GHC than my trusty 28-month-old laptop. Building devel2 on a fresh checkout takes just about an hour. By contrast, my laptop is done after 30 minutes of work (same build settings). The