1 |
On 2007-01-03, Alan McKinnon <alan@××××××××××××××××.za> wrote: |
2 |
> On Wednesday 03 January 2007 15:17, Nelson, David (ED, PAR&D) wrote: |
3 |
> |
4 |
>> I moved to amarok, I might give audacious a shot. |
5 |
>> |
6 |
>> What about noatun for a smallish player? Not sure on it's RAM usage. |
7 |
>> Also look at Quod Libet or Banshee which are meant to be similar in |
8 |
>> features to amarok but lighter in terms of resource usage (or so I |
9 |
>> hear). |
10 |
>> |
11 |
>> David |
12 |
> |
13 |
> David, this reply isn't directed at you. You just happen to be the most |
14 |
> recent post and a convenient reply point. |
15 |
> |
16 |
> Throughout this thread many people have commented on audacious being a |
17 |
> resource hog of monumental proportions. Every single one of them is |
18 |
> wrong and this myth really needs to be debunked. Here's why: |
19 |
> |
20 |
> Look at the libs it links against: |
21 |
|
22 |
[...] |
23 |
|
24 |
> It's those libs that are using the memory, not audacious. Those are |
25 |
> shared libs, meaning many other apps on the system use them |
26 |
|
27 |
That's only relevent if there are other apps running that use |
28 |
those libraries. |
29 |
|
30 |
Even if you assume they _are_ all used by other apps, audacious |
31 |
still uses huge amounts of non-shared memory: |
32 |
|
33 |
Here's my "top" display sorted by memory usage: |
34 |
|
35 |
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND |
36 |
|
37 |
2743 root 15 0 56604 33m 9.9m S 0.0 2.2 10:59.72 X |
38 |
20384 grante 15 0 58696 14m 9696 R 0.0 1.0 0:00.54 audacious |
39 |
2771 grante 15 0 32796 12m 7968 S 0.0 0.8 0:04.56 xfce4-session |
40 |
2782 grante 15 0 31176 9784 6968 S 0.0 0.6 0:04.66 xfce4-panel |
41 |
7195 root 18 0 20692 9200 4476 S 0.0 0.6 0:00.41 apache2 |
42 |
2784 grante 15 0 32304 9096 7076 S 0.0 0.6 0:31.95 gkrellm |
43 |
2773 grante 15 0 30912 8876 5832 S 0.0 0.6 0:03.89 xfce-mcs-manage |
44 |
2780 grante 18 0 13508 8352 6052 S 0.0 0.5 0:09.53 xfdesktop |
45 |
7696 roundup 18 0 11400 7268 1464 S 0.0 0.5 0:00.41 roundup-server |
46 |
2778 grante 15 0 12488 7148 5740 S 0.0 0.5 0:07.98 xftaskbar4 |
47 |
18057 apache 17 0 20692 6672 1924 S 0.0 0.4 0:00.00 apache2 |
48 |
18058 apache 20 0 20692 6672 1924 S 0.0 0.4 0:00.00 apache2 |
49 |
18059 apache 19 0 20692 6672 1924 S 0.0 0.4 0:00.00 apache2 |
50 |
|
51 |
The X server is using 56M of virtual memory with 33M resident |
52 |
and 10M shared. Audacious is using 58M of with 14M resident |
53 |
and 10M shared. |
54 |
|
55 |
> and the total memory they consume is used by all apps that use |
56 |
> the libs. And, every one of those libs (apart from |
57 |
> libaudacious) can reasonably be expected to be in use already |
58 |
> on any desktop machine running X |
59 |
|
60 |
Nonsense. Audacious is using 44MB of non-shared virtual memory |
61 |
on my system. 44MB out of 58MB is not shared. |
62 |
|
63 |
> Here's 'free' before and after I started audacious in another session: |
64 |
> |
65 |
> nazgul ~ # free |
66 |
> total used free shared buffers |
67 |
> cached |
68 |
> Mem: 2076984 1844696 232288 0 246056 |
69 |
> 1220848 |
70 |
> -/+ buffers/cache: 377792 1699192 |
71 |
> Swap: 0 0 0 |
72 |
> nazgul ~ # free |
73 |
> total used free shared buffers |
74 |
> cached |
75 |
> Mem: 2076984 1851528 225456 0 246060 |
76 |
> 1222324 |
77 |
> -/+ buffers/cache: 383144 1693840 |
78 |
> Swap: 0 0 0 |
79 |
> |
80 |
> So starting audacious consumed an extra 6M of memory - that's nowhere |
81 |
> near the 240M other posters are incorrectly stating it uses. |
82 |
|
83 |
I've no idea where the number 240M came from, you didn't hear |
84 |
it from me. It's about 14MB of resident (6MB reduction in |
85 |
"free" memory) on my system, which makes it the second largest |
86 |
memory user (second only to the X server). |
87 |
|
88 |
> So, anyone that says audacious is a resource hog is plain flat |
89 |
> out wrong |
90 |
|
91 |
You don't think that 58M of virtual memory usage isn't a |
92 |
resource hog when the X server only requires 56M and the next |
93 |
largest program is 32M? Virtual memory _is_ a resource, |
94 |
though not an expensive one. |
95 |
|
96 |
> and does not know how the Linux virtual memory system works. |
97 |
> It is complex and almost impossible to know what is going on |
98 |
> at any instant in time, but that's no excuse for people being |
99 |
> wrong by a factor of 500% |
100 |
|
101 |
-- |
102 |
Grant Edwards grante Yow! All this time I've |
103 |
at been VIEWING a RUSSIAN |
104 |
visi.com MIDGET SODOMIZE a HOUSECAT! |
105 |
|
106 |
-- |
107 |
gentoo-user@g.o mailing list |