#4421: Compilation performance regression
---------------------------------+------------------------------------------
    Reporter:  simonmar          |        Owner:  igloo       
        Type:  bug               |       Status:  new         
    Priority:  highest           |    Milestone:  7.0.1       
   Component:  Compiler          |      Version:  6.12.3      
    Keywords:                    |     Testcase:              
   Blockedby:                    |   Difficulty:              
          Os:  Unknown/Multiple  |     Blocking:              
Architecture:  Unknown/Multiple  |      Failure:  None/Unknown
---------------------------------+------------------------------------------

Comment(by igloo):

 With the patch, I was seeing
 {{{
   70,966,109,224 bytes allocated in the heap
   10,517,401,920 bytes copied during GC
       88,885,320 bytes maximum residency (67 sample(s))
       19,679,064 bytes maximum slop
              273 MB total memory in use (0 MB lost due to fragmentation)

   INIT  time    0.00s  (  0.00s elapsed)
   MUT   time   74.56s  ( 77.79s elapsed)
   GC    time   78.38s  ( 78.31s elapsed)
   EXIT  time    0.00s  (  0.00s elapsed)
   Total time  152.95s  (156.10s elapsed)
 }}}
 but after
 {{{
 Wed Oct 20 14:15:39 BST 2010  Ian Lynagh <[email protected]>
   * Avoid hanging on to old unfoldings; fixes #4367 (compiler space
 regression)
 Wed Oct 20 15:37:10 BST 2010  Ian Lynagh <[email protected]>
   * Don't seq unfoldings
 }}}
 I see
 {{{
   46,804,639,544 bytes allocated in the heap
    7,954,212,312 bytes copied during GC
      123,843,728 bytes maximum residency (47 sample(s))
       20,877,992 bytes maximum slop
              377 MB total memory in use (0 MB lost due to fragmentation)

   INIT  time    0.00s  (  0.00s elapsed)
   MUT   time   54.89s  ( 58.56s elapsed)
   GC    time   55.02s  ( 55.03s elapsed)
   EXIT  time    0.00s  (  0.00s elapsed)
   Total time  109.91s  (113.59s elapsed)
 }}}
 so time and allocs look good, but total mem usage is high (but not as high
 as it used to be). Presumably we still sometimes retain old unfoldings,
 but not in cases that happen with the #4367 testcase.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4421#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to