From 9a62bc7609794221a4b43ce52e6b15dd5122804b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 10 May 2016 12:09:28 -0400 Subject: comment --- .../comment_1_0e46ad1844c37a65c532cafe81fd883a._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_1_0e46ad1844c37a65c532cafe81fd883a._comment (limited to 'doc') diff --git a/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_1_0e46ad1844c37a65c532cafe81fd883a._comment b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_1_0e46ad1844c37a65c532cafe81fd883a._comment new file mode 100644 index 00000000..be42b0df --- /dev/null +++ b/doc/forum/recent_propellor_snapshots_cause_ghc_OOMs/comment_1_0e46ad1844c37a65c532cafe81fd883a._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-05-10T16:07:39Z" + content=""" +The enhanced property types in propellor 3.0 are known to have made ghc use +more memory when building it. Building with -O0 helped a lot for me, and +it's doing ok on a 500 mb memory machine. So I recommend -O0 in your cabal +file if you don't have that already. + +I wrote down my memory benchmarks here: + +"""]] -- cgit v1.2.3