[commit: ghc] master: Bump haddock.base max_bytes_used (8df7fea)

[Joachim Breitner]

Hi,


Am Freitag, den 01.08.2014, 23:27 +0200 schrieb Joachim Breitner:
> Am Freitag, den 01.08.2014, 20:28 +0000 schrieb Simon Peyton Jones:
> > Urk.  It's quite surprising that this particular change would increase allocation significantly.
> > I wonder whether it just pushed it over the threshold.
> 
> I’m confident it was not just that:
> 
> ~/logs $ fgrep 'Deviation   haddock.base(normal) max_bytes_used'  $(cd ghc-master; git log --oneline --first-parent db19c665ec5055c2193b2174519866045aeff09a..HEAD | cut -d\  -f1| (cd ..; while read x ; do test -e $x.log && echo $x.log; done) |tac )|tail -n 25
> 6fa6caa.log:    Deviation   haddock.base(normal) max_bytes_used:       2.2 %
> a0ff1eb.log:    Deviation   haddock.base(normal) max_bytes_used:      -1.0 %
> 0be7c2c.log:    Deviation   haddock.base(normal) max_bytes_used:       2.2 %
> dc7d3c2.log:    Deviation   haddock.base(normal) max_bytes_used:       2.2 %
> 7381cee.log:    Deviation   haddock.base(normal) max_bytes_used:       2.2 %
> fe2d807.log:    Deviation   haddock.base(normal) max_bytes_used:       2.2 %
> bfaa179.log:    Deviation   haddock.base(normal) max_bytes_used:      -0.9 %
> 1ae5fa4.log:    Deviation   haddock.base(normal) max_bytes_used:      11.0 %
> c97f853.log:    Deviation   haddock.base(normal) max_bytes_used:      11.0 %
> fd47e26.log:    Deviation   haddock.base(normal) max_bytes_used:      11.2 %
> bdf0ef0.log:    Deviation   haddock.base(normal) max_bytes_used:      11.1 %
[..]

> Interestingly, bytes_allocated did not change a bit!

your surprise made me investigate further. Could this have been caused
by this change to how I run the testsuite, which I did roughly around
that time?

-run make -C testsuite fast VERBOSE=4 THREADS=8
+run make -C testsuite fast VERBOSE=4 THREADS=8 NoFibRuns=15

.... 

No, no difference.

But the value changed again:

d4d4bef.log:    Deviation   haddock.base(normal) max_bytes_used:      11.2 %
8df7fea.log:    Deviation   haddock.base(normal) max_bytes_used:      -0.0 %
3faff73.log:    Deviation   haddock.base(normal) max_bytes_used:      -0.0 %
0336588.log:    Deviation   haddock.base(normal) max_bytes_used:      -0.2 %
02975c9.log:    Deviation   haddock.base(normal) max_bytes_used:      -0.1 %
578fbec.log:    Deviation   haddock.base(normal) max_bytes_used:      -0.2 %
e69619e.log:    Deviation   haddock.base(normal) max_bytes_used:       0.0 %
105602f.log:    Deviation   haddock.base(normal) max_bytes_used:      -0.2 %
fbd0586.log:    Deviation   haddock.base(normal) max_bytes_used:      -6.5 %
ab90bf2.log:    Deviation   haddock.base(normal) max_bytes_used:      -6.5 %
f293931.log:    Deviation   haddock.base(normal) max_bytes_used:      -6.6 %

and fbd0586 really looks harmless.

Not sure what is going on here. I find the changes to be too big (and
within a certain range of commits too deterministic) to be just the
consequence of RTS timer noise. 


Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
  mail at joachim-breitner.de • http://www.joachim-breitner.de/
  Jabber: nomeata at joachim-breitner.de  • GPG-Key: 0xF0FBF51F
  Debian Developer: nomeata at debian.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20140802/092202c0/attachment.sig>