On Fri, Sep 12, 2008 at 2:30 PM, Vlad Skvortsov <[EMAIL PROTECTED]> wrote:
> How do I figure out what exactly in 'serialize' takes so much time?
>
At this point, I don't know any more -- I can't see what inherited
costs serialize could have that don't come from one of the cost
centres you've inser
Tim Chevalier wrote:
When you build your own code with -prof, GHC automatically links in
profiling versions of the standard libraries. However, its profiling
libraries were not built with -auto-all (the reason is that adding
cost centres interferes with optimization). To build the libraries
with
On Wed, Sep 10, 2008 at 12:31 PM, Vlad Skvortsov <[EMAIL PROTECTED]> wrote:
> Hmm, that's a good point! I didn't think about it. Though how do I make GHC
> link in profiling versions of standard libraries? My own libraries are built
> with profiling support and I run Setup.hs with --enable-library-
Tim Chevalier wrote:
2008/9/8 Vlad Skvortsov <[EMAIL PROTECTED]>:
Posting to cafe since I got just one reply on [EMAIL PROTECTED] I was suggested
to
include more SCC annotations, but that didn't help. The 'serialize' function
is still reported to consume about 32% of running time, 29% inheri
2008/9/8 Vlad Skvortsov <[EMAIL PROTECTED]>:
> Posting to cafe since I got just one reply on [EMAIL PROTECTED] I was
> suggested to
> include more SCC annotations, but that didn't help. The 'serialize' function
> is still reported to consume about 32% of running time, 29% inherited.
> However, fun
Posting to cafe since I got just one reply on [EMAIL PROTECTED] I was suggested
to include more SCC annotations, but that didn't help. The 'serialize'
function is still reported to consume about 32% of running time, 29%
inherited. However, functions called from it only account for about 3%
of t
