[Haskell-cafe] What could possibly be the reason of new GC-related problems after upgrading from ghc-7.6 to ghc-7.8.3 ?

[ducis]

I have done heap profiling on 7.8 and identified several hot spots but returning to 7.6 requires pretty a lot of configuration and waiting. There are hotspots, but as I have mentioned the code is convoluted and I don't think anyone will be able to really understand the code snippets if I post them here. I'm mainly looking for general hints and heuristics about how the GC would behave differently when upgraded to 7.8.






At 2014-11-18 22:24:25, "Carter Schonwald" <carter.schonwald at gmail.com> wrote:


Have you done any heap profiling? Eg 7.6 vs 7.8 heap profiles?

On Nov 18, 2014 8:45 AM, "ducis" <ducis_cn at 126.com> wrote:

Recently I revived one of my projects set aside a year ago. As I'm an archlinux user, the ghc version has now inevitably become 7.8.3.  Unfortunatly, the program starts to somehow have very bad GC performance (less than 50% productivity) . While I don't have the statistics of the older versions I'm pretty sure the current version has become visually less responsive. And if the user performs a series of actions in quick succession, the heap is not garbage collected in time and overflows. If the user performs the same actions with longer pauses then everything is fine.  The GC seems to have become more loose in 7.8.
There is quite a large underdocumented pile of code so I don't think posting it here would help.  But can anyone give me a hint about what could be the reason?




_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe at haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20141118/fcba06f7/attachment.html>