Since this topic is philosophical to begin with, "What does a FS box do when idle, and if a tree fell in the woods while a FS box was in a nearby cabin would a bear shit in the woods....."
Another philosophical question would be, If a mailing-list thread persisted for more than 6 hours would it take more or less time to just change the code to make people stop complaining about free software than it does to politely not concern one's self with the issue. I chose the first option, you can update to trunk now and probably see your precious 0.0% so you can get absolutely no use from your computer. As a side note, my change effectively proves that the performance of pthread's mutexing and conditional broadcast implementation has gone downhill since the version on CentOS.
On Tue, Mar 2, 2010 at 10:53 AM, Sergey Okhapkin <sos@sokhapkin.dyndns.org> wrote:
A program should not be visible in "top" when idle. That's my point.
That's a dangerous assumption. Do really know for a certainty that a program "should not" be visible in top when it's "idle"? Like Tony said below, "idle" is misleading. FreeSWITCH is working its but off when you think it's "idle." Make 100 simultaneous calls and see what the CPU usage is. I think you'll be happy with the results.
For the record, we are going to start a wiki page that explains all of this. It's kind of analogous to the whole "Linux eats all my RAM" discussion. We should have something documented in a few days.
-MC
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org