Opened 11 years ago
Last modified 5 years ago
#10163 closed bug
Haiku devours RAM on old computer — at Version 3
Reported by: | Giova84 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | System | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description (last modified by )
hrev 46301
Well, i installed again Haiku on an old computer: an Acer Veriton 9100, which is provided with 256 MiB of DRAM. The last time which i have used Haiku on this pc, I was using Alpha 3, but due to bug #8136, i didn't used often this PC. In anyway, differently from the last time, now Haiku DEVOURS the RAM on this PC. Just opening WebPositive (also without any webpage opened) and i can see 241 MiB of ram occupied, and opening applications, take a while. Eg. opening the "About this system" take about 5 seconds. The situation is worst if i attempt to open more complex apps. Obviously i have activated the virtual memory (with auto management). But Haiku, on this computer, is almost unusable. Obviously i don't pretend that this PC should work like a dual core with 6 GiB of ram (my main pc), but, to do a comparision, Windows XP works decently on this Acer Veriton. Maybe the work on the Scheduler http://www.haiku-os.org/blog/paweł_dziepak/2013-10-21_scheduler_work_progress will help the situation?
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Yeah, obviously you're right. I mentioned the scheduler here, because i was reading this (related) ticket https://dev.haiku-os.org/ticket/8136#comment:7
Maybe is better if i only use Haiku on my main pc :-)
comment:3 by , 11 years ago
Description: | modified (diff) |
---|
Please use proper links to tickets and comments, ie. #8136 or [ticket:8136]
or [ticket:8136#comment:1]
.
If you're swapping, the scheduler isn't going to do anything for you. It's simply a question of what's using up all the memory, though given that nightlies are built with various debug flags activated, chances are some of that is going to increase mem consumption anyhow.