Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: System Resources -- Memory handling (Read 2840 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

System Resources -- Memory handling

I have been an avid foobar user for some time now, with no complaints. But I do have a question. It is frequently stated that foobar better utilizes system resources than winamp, so I did a comparison on memory usage.

In that comparison, I noticed (first of all), that in general winamp and foobar use comparable resources. However, this is not true initially. When I first open foobar (w/ basic plugins, no looks or anything special) it takes about 24-28 megs of memory. Only after minimizing it does that number go down to about 6 megs. If I maximize again, it utilizes between 6 and 12 megs.

Any comments? Why is the memory usage so high initially? In general, how much system resources should foobar be utilizing?

System Resources -- Memory handling

Reply #1 –
Quote
I have been an avid foobar user for some time now, with no complaints. But I do have a question. It is frequently stated that foobar better utilizes system resources than winamp, so I did a comparison on memory usage.

In that comparison, I noticed (first of all), that in general winamp and foobar use comparable resources. However, this is not true initially. When I first open foobar (w/ basic plugins, no looks or anything special) it takes about 24-28 megs of memory. Only after minimizing it does that number go down to about 6 megs. If I maximize again, it utilizes between 6 and 12 megs.

Any comments? Why is the memory usage so high initially? In general, how much system resources should foobar be utilizing?
[a href="index.php?act=findpost&pid=282518"][{POST_SNAPBACK}][/a]


It depends from many factors:
- installed plugins
- plugins enabled in dsp chain
- output buffer size
- files in playlists ( more files - bigger memory consumption )

And remember, results from Tasks Manager may be innacurate!

System Resources -- Memory handling

Reply #2 –
Quote
Quote
I have been an avid foobar user for some time now, with no complaints. But I do have a question. It is frequently stated that foobar better utilizes system resources than winamp, so I did a comparison on memory usage.

In that comparison, I noticed (first of all), that in general winamp and foobar use comparable resources. However, this is not true initially. When I first open foobar (w/ basic plugins, no looks or anything special) it takes about 24-28 megs of memory. Only after minimizing it does that number go down to about 6 megs. If I maximize again, it utilizes between 6 and 12 megs.

Any comments? Why is the memory usage so high initially? In general, how much system resources should foobar be utilizing?
[a href="index.php?act=findpost&pid=282518"][{POST_SNAPBACK}][/a]


It depends from many factors:
- installed plugins
- plugins enabled in dsp chain
- output buffer size
- files in playlists ( more files - bigger memory consumption )

And remember, results from Tasks Manager may be innacurate!
[a href="index.php?act=findpost&pid=282528"][{POST_SNAPBACK}][/a]


I understand that memory usage depends on plugins, but the differences I mentioned should not (theoretically--unless there is a memory leak). The mere act of minimizing the window reduces the amount of memory used, even after that window is restored to its original setting. Though the figures are different, the same phenomenom occurs with foobar "out of the box." So the question is: what is it about minimizing the window that adjusts the resources used, and why do those resources stay smaller after the window has been restored?

System Resources -- Memory handling

Reply #3 –
Windows Task Manager -> View -> Select Columns... -> Virtual Memory Size.
 

System Resources -- Memory handling

Reply #4 –
Quote
Windows Task Manager -> View -> Select Columns... -> Virtual Memory Size.
[a href="index.php?act=findpost&pid=282546"][{POST_SNAPBACK}][/a]


For me, at least, the virtual memory allocation remains (relatively) constant when foobar is minimized, meaning the total memory utilized still reduces by approximately 30% when minimized.