On Tue, Jan 20, 2009 at 6:03 PM, Corey O'Connor <[email protected]> wrote:
> 2) The profiler doesn't exactly lie about where time is spent but > doesn't always give the expected results. The time and allocations > that appear to occur within a given cost center sometimes come from > thunks that are reduced within that cost center. Which can be > misleading since those thunks could have been produced elsewhere. > While adding strictness doesn't always result in better performance it > can place the cost of some thunks "closer" to their producers. Perhaps > I'm wrong here, but from my experience this is correct. I guess you mean the cost of "entering" the thunk is attributed to the consumer... Otherwise, since a program can be only a few big thunks, the profiler would be of little interest. This is of course difficult to talk about unless we have a good knowledge of the GHC RTS. :/ -- JP --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
