3 ms·
The problem with the library doing this is you end up with the same issue as in Haskell: you accumulate thunks and both memory use and location of CPU hotspots
by masklinn 7y ago
The problem with the library doing this is you end up with the same issue as in Haskell: you accumulate thunks and both memory use and location of CPU hotspots becomes much harder to predict and troubleshoot.
- zzzeek 7y agoso...turn off the "thunking" feature while you are debugging.
- JeremyBanks 7y agoThat won't help when you're debugging the performance implications of thunking.
- zzzeek 7y agocompare memory / callcounts / time spent with thunking turned on vs. off would give a good idea of it. i can say for my side of things thunking is a super huge performance gain as it allows for quick gathering of expression intent and then the computation side on the other side of a cache.