Re: [9fans] Kernel panic when compiling Go on native Plan 9

[steve <steve@quintile.net>]

i believe 8l uses its own storage allocator, but coul easily be tweeked to use malloc and free
by hacking the sources a little (global search and replace), if memory serves 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 <quanstro@quanstro.net> wrote:

> On Fri Nov  2 09:44:43 EDT 2012, pavel.klinkovsky@gmail.com wrote:
>>> How much memory does your system have?
>> 
>> - 512 MB RAM
>> - 512 MB swap
>> 
>>> 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.
>> 
>> I see.
>> I can confirm when the kernel panic occured I saw (in stats):
>> - full RAM
>> - small portion of swap occupied
> 
> i might give the 9front kernel a go.  i think that cinap spent
> some time trying to make swap work a little bit.
> 
> 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.
> 
> - erik