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

Austin Seipp austin at well-typed.com
Mon Aug 4 11:04:14 UTC 2014


This is also happening on Phabricator, which is causing the buildbot to choke:

https://phabricator.haskell.org/D112#4

On Mon, Aug 4, 2014 at 6:02 AM, Edward Z. Yang <ezyang at mit.edu> wrote:
> Yes, on my box, this test is now failing (because the stat is too good):
>
>     Expected    haddock.base(normal) max_bytes_used: 127954488 +/-10%
>     Lower bound haddock.base(normal) max_bytes_used: 115159039
>     Upper bound haddock.base(normal) max_bytes_used: 140749937
>     Actual      haddock.base(normal) max_bytes_used: 113167424
>     Deviation   haddock.base(normal) max_bytes_used:     -11.6 %
>
> Cheers,
> Edward
>
> Excerpts from Simon Peyton Jones's message of 2014-08-04 08:21:50 +0100:
>> Ha.  max_bytes_used is vulnerable to exactly when gc strikes, so I'm disinclined to get stressed about this.  I was mis-reading it as bytes-allocated.  Interestingly it doesn't happen for me.
>>
>> Simon
>>
>> | -----Original Message-----
>> | From: ghc-devs [mailto:ghc-devs-bounces at haskell.org] On Behalf Of
>> | Joachim Breitner
>> | Sent: 01 August 2014 22:27
>> | To: ghc-devs at haskell.org
>> | Subject: Re: [commit: ghc] master: Bump haddock.base max_bytes_used
>> | (8df7fea)
>> |
>> | Hi,
>> |
>> |
>> | 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 %
>> | 58ed1cc.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.0 %
>> | 1c1ef82.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.2 %
>> | 52188ad.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.0 %
>> | 3b9fe0c.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.2 %
>> | 6483b8a.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.0 %
>> | 9d9a554.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.2 %
>> | 028630a.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.2 %
>> | aab5937.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.0 %
>> | 6c06db1.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.0 %
>> | 2989ffd.log:    Deviation   haddock.base(normal) max_bytes_used:
>> | 11.1 %
>> | 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 %
>> | 02975c9.log:    Deviation   haddock.base(normal) max_bytes_used:      -
>> | 0.1 %
>> |
>> |
>> | (If this were a bytes_allocated test I could also show you nice graphs
>> | like http://ghcspeed-nomeata.rhcloud.com/timeline/?exe=2&base=2%
>> | 2B68&ben=tests%2Falloc%2FT6048&env=1&revs=50&equid=on but I didn’t add
>> | the max_bytes_used tests yet.)
>> |
>> | Interestingly, bytes_allocated did not change a bit!
>> |
>> | Greetings,
>> | Joachim
>> |
>> | --
>> | Joachim “nomeata” Breitner
>> |   mail at joachim-breitner.dehttp://www.joachim-breitner.de/
>> |   Jabber: nomeata at joachim-breitner.de  • GPG-Key: 0xF0FBF51F
>> |   Debian Developer: nomeata at debian.org
>>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs



-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/


More information about the ghc-devs mailing list