in reply to Multithreaded Server Crashes under heavy load

First pass: Change use threads; to use threads stack_size => 4096; and see if things get better.

Next, use whatever tools are available on your system to instrument memory, cpu and socket activity for the process as it is running and capture it to a file. Make that log (sanitised as appropriate) available on line and post a link to it.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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.

RIP Neil Armstrong
div

Replies are listed 'Best First'.
Re^2: Multithreaded Server Crashes under heavy load
by rmahin (Scribe) on Aug 29, 2012 at 17:29 UTC
    Made the change to use threads but it produced the same result. Looking for a tool to use to capture the information requested now. Is there a tool that you could recommend that can capture all of that information on a Windows environment? Thanks.
[reply]
      Is there a tool that you could recommend that can capture all of that information on a Windows environment?

      Yes. Type perfmon.exe into a command line.

      There is a bit of a learning curve involved in using it, but it is gui with pretty extensive help built in.

      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      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.

      RIP Neil Armstrong
[reply]
[d/l]
        Ok, so heres the link to the comma delimited CSV file perfmon generated. Did not see how to get it to generate socket information for a specific process though. Also, the thing doesn't show that perl ever reached 100% cpu usage, but using the task manager shows that it spawns multiple perl processes, and that cpu usage is maxed for a while, eventually all but one perl process disappears from the task manager, cpu usage drops back down, and then the program is unresponsive.

        https://dl.dropbox.com/u/19686501/RXD_000006.csv

        Made this log by adding a new counter log, and then adding various process counters. If this was incorrect let me know.

[reply]

In Section Seekers of Perl Wisdom