I have a question about a memory size for socket conections. Whith a
POE::Component::Server::TCP module I make a server. In one test make 5000
conections in 10 minutes (test conections).
After the test the memory is this:
$ cat /proc/3565/status | egrep "^(State|VmSize|VmRSS)"
State: S (sleeping)
VmSize: 9734 kB
VmRSS: 8120 kB
Next of test conections is this:
$ cat /proc/3565/status | egrep "^(State|VmSize|VmRSS)"
State: S (sleeping)
VmSize: 14348 kB
VmRSS: 11180 kB
I delete all hash my hash create for work this conections. But I don't now
why low memory next close all conections (I see in netstat don't exist any
conection to the server).
Thanks.
PD: Sorry for my english.
--
--
Gabriel Perez S.
System & Network Development
-
RunSolutions
Open Source It Consulting
-
email: gpe...@runsolutions.com
Mov: 649 98 99 91
tel: 902 88 99 79
fax: 902 88 87 61
Paseo del Borne nº 15 - 6ª Planta
07012 - Palma de Mallorca
Baleares España
> Hi,
>
> I have a question about a memory size for socket conections. Whith a
> POE::Component::Server::TCP module I make a server. In one test
> make 5000
> conections in 10 minutes (test conections).
>
> After the test the memory is this:
>
> $ cat /proc/3565/status | egrep "^(State|VmSize|VmRSS)"
> State: S (sleeping)
> VmSize: 9734 kB
> VmRSS: 8120 kB
>
> Next of test conections is this:
>
> $ cat /proc/3565/status | egrep "^(State|VmSize|VmRSS)"
> State: S (sleeping)
> VmSize: 14348 kB
> VmRSS: 11180 kB
>
>
> I delete all hash my hash create for work this conections. But I
> don't now
> why low memory next close all conections (I see in netstat don't
> exist any
> conection to the server).
>
> Thanks.
Your report of increased memory use from POE::Component::Server::TCP
is not the first. I suspect that recent patches to the module, or to
POE::Filter modules, have introduced a memory leak.
--
Rocco Caputo - rca...@pobox.com
> Your report of increased memory use from POE::Component::Server::TCP is
> not the first. I suspect that recent patches to the module, or to
> POE::Filter modules, have introduced a memory leak.
I've used Devel::Size to great affect in debugging problems of this
nature. POE::API::Peek has some memory-size-grabbing features that might
be helpful and use Devel::Size
sungo