ASU - out of memory?

Tilman Baumann tilman at
Fri Aug 22 10:39:50 CEST 2008

Am 22.08.2008 um 02:50 schrieb Carsten Haitzler (The Rasterman):

>> A 128Mio space of memory is not that huge, especially if you want to
>> use it for something cool and you will at some points pass this mark
>> and things will die; given the current algorithm it might not be
>> something you want to get killed.
> 128m is massive. it's unimaginably huge. if you need more you need  
> to look hard
> at what it is you are doing, and how. seriously. for the kind of  
> processing
> power, storage ability and display ability of this device... - and  
> no. not
> saying "640k is enough for everyone". i am saying that 128m is a  
> lot. people
> who don't think so are incredibly spoilt. possibly are bad  
> programmers who need
> to learn more about memory management or should have their  
> programming licenses
> revoked! :) (ok just kidding there). but seriously - it's a lot.  
> this is why
> instead of running off to swap for help - which just overflows your  
> ram problems
> onto disk (and sooner or later swap fills - then what? you haven't  
> fixed the
> original problem - just delayed it).

Yes, 128mb is much.
Yes, memory problems don't go away with swap. They are just a bit more  
easy to handle.
Yes, Overflowing swap is still a problem. But this means no one cared  
to solve the problem first.

And even if 128mb are much. Why waste memory?
(overcommit off + emergency threshold < 100% for save app shutdown)

More information about the community mailing list