in reply to Re^2: Status of memory leak problem?
in thread Status of memory leak problem?

Which platform, and what output from the program?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"I'd rather go naked than blow up my ass"

Replies are listed 'Best First'.
Re^4: Status of memory leak problem?
by zwon (Abbot) on Apr 03, 2010 at 19:41 UTC

    It's Ubuntu 9.10, output is like: 

    268 threads/second
242 threads/second
236 threads/second
231 threads/second
230 threads/second
228 threads/second
228 threads/second

    [download]
[reply]
[d/l]

      So, that's

      1. 5.10.1: 3k per thread.
      2. 5.8.9: 1k per thread,

      Solution: use a pool of threads.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
        To use this solution it should be able to pass a socket from main program listener to a worker thread. Is there any way to accomplish this?
[reply]

In Section Seekers of Perl Wisdom