From mboxrd@z Thu Jan 1 00:00:00 1970 References: <4A0E7310-9D9D-45C5-88A3-62B4A3191267@quintile.net> <20121103163103.GA48522@intma.in> <5cff355142bfe83410dce1c3fc321f25@kw.quanstro.net> <20121103165100.GA63071@intma.in> <7cd2c11374f75d628a5bb5e1f1d0919e@kw.quanstro.net> <20121103171322.GA76929@intma.in> In-Reply-To: Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-A1128B03-8C98-4E43-9E8E-B4234B3F5542 Message-Id: <5C93B9D0-0B34-40EA-B96B-2D7B5C31A9F9@bitblocks.com> Content-Transfer-Encoding: 7bit From: Bakul Shah Date: Sun, 4 Nov 2012 10:57:16 -0800 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Kernel panic when allocating a huge memory Topicbox-Message-UUID: d36ea0e2-ead7-11e9-9d60-3106f5b1d025 --Apple-Mail-A1128B03-8C98-4E43-9E8E-B4234B3F5542 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii What is really needed is to have some of your hotshot programmers develop on= 3+ year old "average" computers. Their code bloat will reduce when their ow= n productivity suffers due to slow machines. Still there will be cases where a lean program will run out of memory. It sh= ould do its own memory management. For instance, don't try to map in multi G= B files in their entirety if you are justvstreaming data! On Nov 4, 2012, at 6:58 AM, Charles Forsyth wrot= e: > It needn't. Today, with the price of RAM, as many have noted, it's probabl= y not worth the code and complexity > (though there needn't be much of either), but it can be designed and made t= o work well. >=20 > Also, despite the low cost of RAM, the systems still run out: my 3 Gbyte n= otebook running Chrome under Linux > can run out. What Linux then does with no paging file is not pleasant, so I= give it a small one, and it still thrashes > trying to reclaim enough memory to continue. Pathetic. >=20 > My new 4Gb notebook has the memory soldered in (Samsung Series 9). >=20 > On 4 November 2012 14:18, hiro <23hiro@gmail.com> wrote: > that paging sucks is not a very new discovery. >=20 --Apple-Mail-A1128B03-8C98-4E43-9E8E-B4234B3F5542 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
What is really needed is t= o have some of your hotshot programmers develop on 3+ year old "average" com= puters. Their code bloat will reduce when their own productivity suffers due= to slow machines.

Still there will be cases where a= lean program will run out of memory. It should do its own memory management= . For instance, don't try to map in multi GB files in their entirety if you a= re justvstreaming data!

On Nov 4, 2012, at 6:5= 8 AM, Charles Forsyth <charl= es.forsyth@gmail.com> wrote:

It needn't. Toda= y, with the price of RAM, as many have noted, it's probably not worth the co= de and complexity
(though there needn't be m= uch of either), but it can be designed and made to work well.

Also, despit= e the low cost of RAM, the systems still run out: my 3 Gbyte notebook runnin= g Chrome under Linux
can run out. What L= inux then does with no paging file is not pleasant, so I give it a small one= , and it still thrashes
trying to reclaim enough memory to continue. Path= etic.

M= y new 4Gb notebook has the memory soldered in (Samsung Series 9).

On 4 November 2012 14:18, hiro <23hiro@gmail.c= om> wrote:
that paging sucks is not a very new discovery.

= --Apple-Mail-A1128B03-8C98-4E43-9E8E-B4234B3F5542--