memory management
Mar. 24th, 2005 02:38 pmIn my experience, Linux is as bad as Windows. I'm routinely having to wait 5 minutes for my screen to process a simple "minimize" click.
What the hell is my computer doing that's keeping it so busy? My guess is it's swapping memory with the HD, since this only happens when I have "too many" things open.
Another solution would be to save the inactive current processes to the HD, free up the memory, and *only* load them up when requested (instead of juggling things around all the time).
Does anyone know how to turn off memory swapping? I would prefer to get an error message: "memory is full". Does anyone know which process corresponds to the screen / user input, so I can up its priority?
Why is the software of today still oblivious to the user's experience?
What the hell is my computer doing that's keeping it so busy? My guess is it's swapping memory with the HD, since this only happens when I have "too many" things open.
Another solution would be to save the inactive current processes to the HD, free up the memory, and *only* load them up when requested (instead of juggling things around all the time).
Does anyone know how to turn off memory swapping? I would prefer to get an error message: "memory is full". Does anyone know which process corresponds to the screen / user input, so I can up its priority?
Why is the software of today still oblivious to the user's experience?
(no subject)
Date: 2005-03-26 07:10 pm (UTC)Your suggestion for saving things to the HD is basically what swapping does. The only difference seems to be in the application being fully inactive until the user (you) reactivates it, instead of waking up to do trivial little things. Sounds like an application level edit to me.
I don't know what you're running, but does your OS allow you to manually "Pause" a process?