<_maniac_>
faulty cable, machine is online and build is still going
<ZirconiumX>
How many cores do you have?
<_maniac_>
only two there.
hdon has joined #ocaml
<ZirconiumX>
You're running -j 10
<ZirconiumX>
That's 500% loading per core
<ZirconiumX>
Or in other words, each file now takes 5x as long to compile
mk9 has quit [Quit: mk9]
<_maniac_>
yeah, I noticed, I thought it was an proctitle error, because I see only one process with no threads and parent make passes -j1 anyway
<ZirconiumX>
_maniac_: perhaps you should turn -j down
kakadu has joined #ocaml
kakadu_ has quit [Ping timeout: 245 seconds]
<ZirconiumX>
In the makefile
<ZirconiumX>
Not the make command line
<_maniac_>
probably it doesn't like `-l1` passed to make
<_maniac_>
hm, makefile? ok.
<ZirconiumX>
PPC64, but only two cores. Are you using a G5?
<_maniac_>
exactly
<ZirconiumX>
That would be another reason why.
webshinra_ is now known as webshinra
<_maniac_>
I know it isn't fastest machine, but waiting for 20 hours got me worried, and that's why I am here.
<ZirconiumX>
Also, are you running in little or big endian? A friend had issues using little endian on those boxes.
hdon has quit [Ping timeout: 276 seconds]
<_maniac_>
BE, and I got my share of endianness issues too
<ZirconiumX>
Truth be told, my raspberry pi 3b+ is faster than your box, and has twice the cores.
<_maniac_>
yes, most probably
<_maniac_>
I wonder why I never noticed -j10 on my laptop.
argent_smith has quit [Quit: Leaving.]
<ZirconiumX>
Maybe it's time to consider an upgrade, _maniac_
<_maniac_>
Hey! I just recently bought it.
<ZirconiumX>
The OCaml compiler is pretty fast, but for that kind of thing, you would have to hack the makefile
<ZirconiumX>
I think -opaque as a compiler flag should help the build
<_maniac_>
but I don't see it using much memory either. whole build just finished in less than a minute. g5 started stuttering after 2GB real ram ended. then I added some swap, couple of times, and the result you saw on screenshot
<_maniac_>
build finished - on i7 laptop
ziyourenxiang has joined #ocaml
<ZirconiumX>
Wait
<ZirconiumX>
That build is running on swap?
<_maniac_>
was running, yes. 2gb ram and 16gb of swap.
<ZirconiumX>
No wonder it's so slow
<_maniac_>
no wonder at all, but why eat 14Gb?
<ZirconiumX>
I'd hazard a guess at the inter-module optimisation OCaml does
<ZirconiumX>
Imagine building every C program with -flto
<ZirconiumX>
That's what OCaml does
<_maniac_>
aha, got it.
<ZirconiumX>
-opaque disables this
<ZirconiumX>
At the cost of performance
<_maniac_>
thank you. going to try this and submit a fix into gentoo
<ZirconiumX>
I'm not sure whether they'd accept it
<_maniac_>
slower build on memory-constrained systems is better than failed build
<ZirconiumX>
It'd be easier to cross-compile at that point
barcabuona has joined #ocaml
<_maniac_>
you see, cross-compiling is keeping machine I am using busy
Haudegen has quit [Read error: Connection reset by peer]
<octachron>
_maniac_, dose3 is a pathological case with flambda (which is an optional optimisating middle-end), you should really disable flambda in this situation
larhat has quit [Quit: Leaving.]
ziyourenxiang has quit [Ping timeout: 268 seconds]
<discord3>
<Perry> So just to note: the difference between RAM speed and disk speed is many orders of magnitude. Once you start paging during a build, you're dead. You cannot do this and expect reasonable performance.
<_maniac_>
I know, I know, I know that very well. I wasn't in a hurry ;)
<_maniac_>
now, reading docs gave impression that I can't use flambda and non-flambda code on same system
<_maniac_>
at least, can't link against each other
<discord3>
<Perry> I believe it is six orders of magnitude. You get that's like 2 million times slower.
<discord3>
<Perry> Pardon, like 200,000 times slower. Still.
<discord3>
<Perry> Something that takes 1 second going to main memory would take 2.3 days if every access had to be to disk. It's that big a difference.
exarkun has quit [Read error: Connection reset by peer]
<octachron>
_maniac_, yes, you cannot mixes flambda and non-flambda code; but taking years to compile code is not exactly doable either
spew has quit [Ping timeout: 265 seconds]
pierpa has joined #ocaml
exarkun has joined #ocaml
<discord3>
<Perry> BTW, the biggest performance increases I've ever experienced have been associated with moving things from disk access to memory access. If, for example, you can put a whole web site into RAM you can saturate pretty damn fast network interfaces, but if you're hitting disk suddenly everything slows to a crawl. SSD is like 100-150x faster than magnetic disk, but still WAY slower than RAM.
<_maniac_>
ok, finding all places where I should put `-opaque` to make it compile is harder than just disabling flambda
<octachron>
_maniac_, note that I am unconvinced that the problem can be solved by -opaque
<_maniac_>
already disabled flambda, now waiting for new compiler
kakadu has quit [Remote host closed the connection]
shinnya has joined #ocaml
hdon has joined #ocaml
spew has joined #ocaml
hdon has quit [Ping timeout: 240 seconds]
zolk3ri has quit [Remote host closed the connection]
BitPuffin has quit [Remote host closed the connection]