OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: me@home on November 29, 2005, 01:18:18 pm
-
I notice that the memory usage is quite strange on my C1K using cacko 1.23.
When I reboot the Z I have: Total Memory 63.787 KB free about 5.500KB (app. fast load off).
When I start Zemu frontend I'll get after finishing it MORE free Ram, using Kino2 means getting lower Ram afterwards...strange.
I notice the cached ram lowers then...
Now I'd like to know: Is the free memory as imprtant as on my home pc or is it just reflashing alone so I have sometimes more and sometimes less free Ram ?
I have no swap file.
PS: I did a search 'memory' and 'memory free' interesting but not enough infos.
-
Does whatever you're using to look at the memory status discriminate between allocated memory and cache (which is just free memory doing something useful until it's needed)?
Si
-
Could be the number of loaded modules.
Iv seen bluez load net and other modules at start up which Iv now dissabled (I dont have any bluetooth devices)
-
thanks for helping.
well I still can't figure out if it's important to have more free Ram or let it be in cache.
on my Windoof and Linux PC's I have as much as possible free Ram (not many autoload ...) on my old PPCs Ram was most times quite important - at least to have more...
has someone PdaXrom installed and can check how much is 'free' ?
-
Isn't chached RAM stuff held in ram, but will be dumped if an app needs the memory? I vaguely remember with my 5500 days, someone telling me to combine free and cached memory to truely know what is available to an app.
Sorry if I'm stating the obvious.
-
- Don't know how much of this is rehash, but Cacko fastloads lots of stuff. If I have nothing fastloaded there's usually about 20MB or so free after a reboot. It varies quite a bit, for some reason.
- Adding KOPI & KAPI fastloaded drops that to around 14MB or so, now that the little memory issue on reboot appears to be resolved.
- I've seen the same thing ... I may only have 2MB "free" (uncached) when I launch an app, and after closing it I'll have some larger amount, sometimes dramatically larger. The system rarely seems to mind, and I've always assumed it's aging cache to get what it needs. It could very easily pop some back into cache after unloading an app, so how it works in any single instance is probably not significant.
- I generally follow the rule that if the system isn't complaining about memory, then don't worry about it. (wink) Cacko's memory applet is pretty good about turning yellow in time to do something rational, and the system has actually only locked up once when I tried to load Opera when it was already yellow. It typically pops a dialog for you to select an application to kill before that happens. It runs slower than molasses in January when that happens, but it almost never crashes. Quite like Linux in general, and quite unlike Winbloze, which just barfs.
- So I wouldn't worry too much about it. Hope this helps...
-
A small advice - have a swap file ready (but not activated) on flash or SD card. As soon as memory applet bar gets yellow, activate the swap ASAP, before Qtopia displays a low memory warning and starts to crawl...
-
A small advice - have a swap file ready (but not activated)
will try it as soon as I get my microdrive.
-
A small advice - have a swap file ready (but not activated)
will try it as soon as I get my microdrive.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106588\"][{POST_SNAPBACK}][/a][/div]
I am completely amazed with how well 1.23 manages memory. I leave a 32MB swap file on my SD, as I see no performance hit. For fun, I launched 10 apps the other day and quickly bounced between them. I was still in the green, a nd performance was great with Opera,all the handcom apps, music player, etc. running.
It's pretty mind blowing.....64MB RAM!!!