2 ms·
Two, well, issues from my experience with gitit (great software by the way): compilation may take huge amounts of RAM compared to what the webapp itself will la
by mbq 13y ago
Two, well, issues from my experience with gitit (great software by the way): compilation may take huge amounts of RAM compared to what the webapp itself will later use -- it is likely that one will need to use some other, metal machine for building. Also, Haskell is doing idle garbage collection which eats CPU even when nothing is happening, and this may become a less or more painful surprise. It can be turned off, though.
- dons 13y ago> idle garbage collection ... Eating CPU when nothing is happening .. Painful surprise Wait, what?
- jcurbo 13y agoI don't have any specific info about what the parent post was talking about, but for those that were curious about Haskell's garbage collector in general (like me), here is a Stack Overflow link with some explanation: http://stackoverflow.com/questions/15236238/current-state-of-haskell-soft-real-time http://stackoverflow.com/questions/15236238/current-state-of... And here is the GHC (Haskell compiler) docs on controlling the garbage collector: http://www.haskell.org/ghc/docs/7.0.1/html/users_guide/runtime-control.html http://www.haskell.org/ghc/docs/7.0.1/html/users_guide/runti...