11 Apr
2005
11 Apr
'05
10:11 p.m.
Perhaps the new mediaproxy-1.3 will fix this. I'm just graping for straws
here.
Regards,
Paul
On Apr 11, 2005 4:55 PM, Ricardo Martinez <rmartinez(a)redvoiss.net> wrote:
Hello list.
Regarding to this issue. These are the results for my "production"
machine after upgrade the Python from 2.3 to 2.4.1.
Since Friday the %MEM is 0.5, as the output of the "top" command indicate
:
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
6131 root 15 0 5460 5460 2492 S 9.9 0.5 119:04 0
mediaproxy.py
So, it works!. For the record i'm using :
OS : Red Hat 9.0
Python : 2.4.1
SER: 0.8.14
mediaproxy : 1.2.1
Regards,
Ricardo Martinez.-
-----Mensaje original-----
De: Ricardo Martinez [mailto:rmartinez@redvoiss.net]
Enviado el: Viernes, 08 de Abril de 2005 18:18
Para: 'Lucas Aimaretto'; serusers(a)lists.iptel.org
Asunto: RE: [Serusers] Mediaproxy still consuming a lot of
RAM resources.
Regarding to this issue
Well, thanks to Lucas, just to test i changed the
pyhton version in
my "lab" server from python2.3 to pyhton2.4.1. I made the
same test with
the rtpgenerator and "voila".
Check it out :
Before 80 simultaneus calls :
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
13915 root 15 0 4628 4628 2068 S 1.0 0.9 0:00
mediaproxy.py
During the test :
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
13915 root 25 0 4864 4864 2068 R 99.9 0.9 0:31
mediaproxy.py
After the test :
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
3356 root 15 0 1600 1600 1036 S 0.0 0.3 0:00 bash
13915 root 15 0 4864 4864 2068 S 0.0 0.9 0:44
mediaproxy.py
0.9 % !!!!!
I made the test a couples of times later and the %MEM used is
still 0.9%.
I guess that it was maybe a problem between the python2.3 and the
mediaproxy? Don't know...
I'm going to change the python version in my production
machine. i'm going
to keep you inform about the results...
Thanks to Lucas...again.
Best Regards,
Ricardo Martinez.-
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
-----Mensaje original-----
De: Ricardo Martinez [mailto:rmartinez@redvoiss.net]
Enviado el: Viernes, 08 de Abril de 2005 17:33
Para: 'Lucas Aimaretto'; serusers(a)lists.iptel.org
Asunto: RE: [Serusers] Mediaproxy still consuming a lot of
RAM resources.
For example now i have 14 simultaneus calls.
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
CPU COMMAND
11760 root 15 0 601M 518M 2396 R 7.2
51.4
69:10 0 mediaproxy.py
When the active calls are 0 again the CPU % reach 0.2%, but
the %MEM is
greater than 51.4%, and always increasing..
A couple of questions.
How you launch mediaproxy?. And in your last mail what are
the pyhton
proccess running.. i don't see the mediaproxy
process running.
Thanks again.
Ricardo.-
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
-----Mensaje original-----
De: Lucas Aimaretto [mailto:lucas@cyneric.com]
Enviado el: Viernes, 08 de Abril de 2005 17:20
Para: 'Ricardo Martinez'; serusers(a)lists.iptel.org
Asunto: RE: [Serusers] Mediaproxy still consuming a lot of
RAM resources.
> But when you check the use of RAM memory in your machine...
> (maybe with the command "top" or the command "free") don't
> you notice a increasing amount of RAM used without being
> released? As i mentioned i have this problem.. this is a
> snippet of the output of the "top" command in my machine:
>
> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
> CPU COMMAND
> 11760 root 15 0 590M 516M 2396 S 0.9
51.2
> 68:15 0 mediaproxy.py
>
> 51.2% of memory used? What version of pyhton are you using?,
> what OS are you using?. Thanks!
Hey!, how many calls where you proxying when you had that usage of
memmory ?
Regards,
Lucas
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.5 - Release Date:
07/04/2005