memory slop (was: Using the GHC heap profiler)

2011-03-22 Thread Tim Docker
On Mon, Mar 21, 2011 at 9:59 AM, I wrote: My question on the ghc heap profiler on stack overflow: http://stackoverflow.com/questions/5306717/how-should-i-interpret-the-output-of-the-ghc-heap-profiler remains unanswered :-( Perhaps that's not the best forum. Is there someone here prepared to

Re: memory slop (was: Using the GHC heap profiler)

2011-03-22 Thread Daniel Fischer
On Wednesday 23 March 2011 03:32:16, Tim Docker wrote: On Mon, Mar 21, 2011 at 9:59 AM, I wrote: My question on the ghc heap profiler on stack overflow: http://stackoverflow.com/questions/5306717/how-should-i-interpret-the- output-of-the-ghc-heap-profiler remains unanswered :-(

Re: memory slop (was: Using the GHC heap profiler)

2011-03-22 Thread John Lato
compact representation) directly from the handle without going through an intervening string format. Also, you'll be better off using a real parser instead of read, which is very difficult to use robustly. John L. From: Tim Docker t...@dockerz.net Subject: memory slop (was: Using the GHC heap

Re: memory slop (was: Using the GHC heap profiler)

2011-03-22 Thread Johan Tibell
On Wed, Mar 23, 2011 at 9:32 AM, Tim Docker t...@dockerz.net wrote:  Productivity  78.2% of total user, 76.5% of total elapsed As a rule of thumb GC time should be less than 10%. This seems strange. The maximum residency of 12MB sounds about correct for my data. But what's with the 59MB of

Re: memory slop (was: Using the GHC heap profiler)

2011-03-22 Thread John Lato
documentation and examples, particularly pEnd. I think this will make a significant difference to your application. John L. Message: 4 Date: Tue, 22 Mar 2011 20:32:16 -0600 From: Tim Docker t...@dockerz.net Subject: memory slop (was: Using the GHC heap profiler) To: glasgow-haskell-users@haskell.org