Quote from ShiftPlusOne on September 15, 2011, 19:02
Quote from ryao on September 15, 2011, 13:59
Quote from ShiftPlusOne on September 15, 2011, 04:49
uclibc and -Os is used to reduce the size of executables on embedded devices where the physical storage space is limited. That's not a problem for Raspberry Pi, since everything runs off the SD card. I am not sure that it does anything to help reduce memory usage when you compare it to the memory used to cache streams, theme graphics and so on.
But yeah, I think it's doable and I'll definitely be giving it a go.
If the executables are smaller, then there is more room in RAM for actual data because the OS does not need to load as many bytes.
I've acknowledged what you said, I am just saying that that's not where the memory optimization needs to come from. We're not trying to shave off a few bytes here.
Then people can use compcache to work around the low memory:
Doubling the effective memory to 512MB through compression should be possible. Depending on how compressible it is, tripling it to 768MB might even be possible.
Note that for anyone reading this, you do not get extra memory from compcache. It just uses your existing memory more efficiently by sacrificing CPU cycles to do it. To avoid running into problems, compcache requires a swap file, so there is no magic memory expander here.
Anyway, on the topic of the swap file, you could increase the memory as much as you want by using a RAM disk on a more powerful system on your network as swap. This would of course incur a performance hit and also link the Raspberry Pi's stability to your network stability, but it would work.