From mboxrd@z Thu Jan 1 00:00:00 1970 References: <3816729a-a9d5-4f63-9850-c7247edae37e@c16g2000yqe.googlegroups.com> <28d5b94e81a770e9521a1b80366b8892@brasstown.quanstro.net> From: steve Content-Type: text/plain; charset=us-ascii In-Reply-To: <28d5b94e81a770e9521a1b80366b8892@brasstown.quanstro.net> Message-Id: <177C8A93-FECA-491E-9958-17D5FFBFB156@quintile.net> Date: Fri, 2 Nov 2012 16:44:34 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: [9fans] Kernel panic when compiling Go on native Plan 9 Topicbox-Message-UUID: d034d838-ead7-11e9-9d60-3106f5b1d025 i believe 8l uses its own storage allocator, but coul easily be tweeked to u= se malloc and free by hacking the sources a little (global search and replace), if memory serve= s me well this trades memory use for speed, and by going back to traditional malloc in go's= 8l you could reduce the ram use but make it quite a bit slower. -Steve On 2 Nov 2012, at 14:00, erik quanstrom wrote: > On Fri Nov 2 09:44:43 EDT 2012, pavel.klinkovsky@gmail.com wrote: >>> How much memory does your system have? >>=20 >> - 512 MB RAM >> - 512 MB swap >>=20 >>> Changeset 14739 grew the Unicode collation tables >>> in the exp/locale/collate package by a considerable >>> amount. The compiler's memory usage now goes above >>> 400 MB when building that package, almost 2.5x the >>> amount used to compile the second heavyweight and >>> 15x the average. >>=20 >> I see. >> I can confirm when the kernel panic occured I saw (in stats): >> - full RAM >> - small portion of swap occupied >=20 > i might give the 9front kernel a go. i think that cinap spent > some time trying to make swap work a little bit. >=20 > i'd wonder though if there were some way to cut down the module > so it doesn't take quite so much memory. even halving it would > mean you could ditch swap. >=20 > - erik