Memory usage on Debian vs. Arch

whargoul · 2008-08-31 17:46:20

Gullible Jones wrote:

Hmm, I'm never using less than 200 MB after a cold boot. I assume you have your graphics hardware's shared memory set to minimum in the BIOS?

I wouldn't know since no such option is availible.

Gullible Jones · 2008-09-01 22:27:13

Huh, there is in my BIOS. It doesn't make any difference though, although it absolutely kills 3D performance.

At any rate, there appears to be something more going on than just graphics hardware stuff. Archlinux CPU usage peaks while when moving a window that overlaps another, but in Debian that doesn't happen... Weird.

I think I'll be switching to Debian Testing for a while on my laptop, actually... I'll probably be keeping Arch on my desktop though, and continue maintaining my AUR packages (though it's fine if someone else wants to adopt them, I'm not a great maintainer).

Meanwhile I'll see if I can reproduce the CPU thing on my desktop.

ihavenoname · 2008-09-02 03:53:59

Gullible Jones wrote:

Huh, there is in my BIOS. It doesn't make any difference though, although it absolutely kills 3D performance.
At any rate, there appears to be something more going on than just graphics hardware stuff. Archlinux CPU usage peaks while when moving a window that overlaps another, but in Debian that doesn't happen... Weird.
I think I'll be switching to Debian Testing for a while on my laptop, actually... I'll probably be keeping Arch on my desktop though, and continue maintaining my AUR packages (though it's fine if someone else wants to adopt them, I'm not a great maintainer).
Meanwhile I'll see if I can reproduce the CPU thing on my desktop.

which packages?

Though I am having similar issues. Btw, can anyone confirm if this is an issue on ubuntu?

Gullible Jones · 2008-09-02 10:26:17

Currently the packages are joss, lalcal, libtxc_dxtn, pymp, and xine-plugin.

As far as CPU usage goes, it still goes up a lot on resizing windows... Looks to me like there's nothing I can do about that. Maybe 2D acceleration just sucks for Intel chipsets.

broch · 2008-09-02 13:18:30

well after cold boot to KDE/nvidia driver (amounts for ~15MB), Arch is using 81MB

It seems that difference is made by setting custom kernel, so this would mean that default debian kernel and default Arch kernel will use different amount of RAM. Additionally each app can be tweaked for bigger or smaller RAM usage. Now using less RAM does not mean that app is in anyway crippled.

iphitus · 2008-09-02 15:17:12

Gullible Jones wrote:

Currently the packages are joss, lalcal, libtxc_dxtn, pymp, and xine-plugin.
As far as CPU usage goes, it still goes up a lot on resizing windows... Looks to me like there's nothing I can do about that. Maybe 2D acceleration just sucks for Intel chipsets.

Works here... the intel drivers are normally pretty good/above average.

You never seem to have any luck

Have you done anything unusual to your xorg.conf? Mine's just the default generated one, with dri enabled.

Gullible Jones · 2008-09-02 16:23:05

My xorg.conf:

Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "SendCoreEvents"
    InputDevice    "Touchpad" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"
    Load  "dri"
    Load  "extmod"
    Load  "xtrap"
    Load  "GLcore"
    Load  "glx"
    Load  "dbe"
    Load  "record"
    Load  "freetype"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
EndSection

Section "InputDevice"
    Identifier  "Touchpad"
    Driver      "synaptics"
    Option      "Protocol" "auto-dev"
    Option      "Device" "/dev/input/mice"
    Option      "SHMConfig"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option        "Protocol" "ImPS/2"
    Option        "Device" "/dev/input/mice"
    Option      "ChordMiddle"
    Option      "EmulateWheel"
    Option      "EmulateWheelButton" "2"
    Option        "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
    Identifier   "Monitor0"
EndSection

Section "Device"
    Identifier  "Card0"
    Driver      "intel"
    Option      "AccelMethod" "XAA"
    Option      "MigrationHeuristic" "greedy"
    Option      "XAANoOffscreenPixmaps"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    DefaultDepth   24
    SubSection "Display"
        Viewport   0 0
        Depth     24
        Modes  "1280x800"
    EndSubSection
EndSection

Section "Extensions"
    Option     "Composite"
EndSection

I don't think I've done anything wrong with it...

Last edited by Gullible Jones (2008-09-02 16:23:37)

whargoul · 2008-09-02 19:13:59

Gullible Jones wrote:

Currently the packages are joss, lalcal, libtxc_dxtn, pymp, and xine-plugin.
As far as CPU usage goes, it still goes up a lot on resizing windows... Looks to me like there's nothing I can do about that. Maybe 2D acceleration just sucks for Intel chipsets.

How far does the CPU usage goes up? Mine spikes at least 15% when maximising urxvt w/ htop.

Gullible Jones · 2008-09-02 19:26:31

Mine spikes about that much when maximizing, but moving windows over each other spikes up to at least 50%, and resizing spikes to 70-100%.

Gullible Jones · 2008-09-04 02:03:18

Hmm. Can anyone give me stats on Rhythmbox's memory usage? It's about 160 MB for me.

(This is really weird. I'm starting to wonder if X has a memory leak or something.)

Edit: N/M this is a Rhythmbox bug... Banshee only uses 50 MB.

Last edited by Gullible Jones (2008-09-04 02:52:00)

Kknd · 2008-09-05 01:58:28

Rhytmbox uses 24mb here (only basic plugins and not much songs)

shining · 2008-09-05 06:10:42

Hm, you need to tell which memory stat you are looking at.
From man top:

n: %MEM -- Memory usage (RES)
A task's currently used share of available physical memory.
o: VIRT -- Virtual Image (kb)
The total amount of virtual memory used by the task. It
includes all code, data and shared libraries plus pages that
have been swapped out.
VIRT = SWAP + RES.
p: SWAP -- Swapped size (kb)
The swapped out portion of a task's total virtual memory image.
q: RES -- Resident size (kb)
The non-swapped physical memory a task has used.
RES = CODE + DATA.
r: CODE -- Code size (kb)
The amount of physical memory devoted to executable code, also
known as the 'text resident set' size or TRS.
s: DATA -- Data+Stack size (kb)
The amount of physical memory devoted to other than executable
code, also known as the 'data resident set' size or DRS.
t: SHR -- Shared Mem size (kb)
The amount of shared memory used by a task. It simply reflects
memory that could be potentially shared with other processes.

VIRT / RES / SHR for rhythmbox here : 156m 51m 20m

Last edited by shining (2008-09-05 06:11:52)

Gullible Jones · 2008-09-05 13:18:23

Was using MEM...

Arch Linux

#26 2008-08-31 17:46:20

Re: Memory usage on Debian vs. Arch

#27 2008-09-01 22:27:13

Re: Memory usage on Debian vs. Arch

#28 2008-09-02 03:53:59

Re: Memory usage on Debian vs. Arch

#29 2008-09-02 10:26:17

Re: Memory usage on Debian vs. Arch

#30 2008-09-02 13:18:30

Re: Memory usage on Debian vs. Arch

#31 2008-09-02 15:17:12

Re: Memory usage on Debian vs. Arch

#32 2008-09-02 16:23:05

Re: Memory usage on Debian vs. Arch

#33 2008-09-02 19:13:59

Re: Memory usage on Debian vs. Arch

#34 2008-09-02 19:26:31

Re: Memory usage on Debian vs. Arch

#35 2008-09-04 02:03:18

Re: Memory usage on Debian vs. Arch

#36 2008-09-05 01:58:28

Re: Memory usage on Debian vs. Arch

#37 2008-09-05 06:10:42

Re: Memory usage on Debian vs. Arch

#38 2008-09-05 13:18:23

Re: Memory usage on Debian vs. Arch

Board footer