in reply to Re^15: Monitor list of threads running
in thread Monitor list of threads running

OK I finally got it working. 

gambit$ perl -Mthreads -e 'use lib "/ssy/nos/thread_libs/lib/lib64/per
+l5/5.8.8/x86_64-linux-thread-multi/";die $threads::VERSION'

I got 1.07 at -e line 1

[download]

But If I run this. I get correct message

#!/usr/bin/perl

use lib "/ssy/nos/thread_libs/lib/lib64/perl5/5.8.8/x86_64-linux-threa
+d-multi/";
use threads;
print "Using threads.pm version $threads::VERSION\n";

Output: Using threads.pm version 1.77

[download]

oh and also If I include path up to /ssy/nos/thread_libs/lib/lib64/ in perl script I get 1.07.

Never the less I got it with you help. thanks so much again.

Replies are listed 'Best First'.
Re^17: Monitor list of threads running
by BrowserUk (Patriarch) on Apr 09, 2010 at 17:12 UTC

    Had you done: 

    perl -Mlib=/ssy/nos/thread_libs/lib/lib64/perl5/5.8.8/x86_64-linux-thr
+ead-multi/ 
-Mthreads -e 'die $threads::VERSION'

    [download]

    The lib path would have been added to before the thread module was loaded, and it would work.

    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]
[d/l]
      Thant worked. Thanks.

      On another note: I will have lots of threads downloading files using Net::FTP, I have noted the each threads uses 10MB size, Can you tell If I even need 10MB per stack size per thread if all I'm doing is downloading files. Max file size will be 1MB.

[reply]
        : I will have lots of threads downloading files using Net::FTP,

        There is a limit to how much benefit you can derive from running downloads concurrently. Namely, the bandwidth of your internet connection. Even if you're sitting on the end of a very fat pipe downloading from independant, throttling servers, I'd seriously doubt you'll see much improvement beyond low 10s of threads. Unless all the servers are on a local Gigabit network.

        Not all of the per-thread memory allocation is stack. Most of it is cloned internal datastructures that you cannot do much about.

        You could try playing with the stack size per the documentation and see what if any difference it makes:

        use threads ('stack_size' => VALUE);

        This sets the default per-thread stack size at the start of the application.

        Perl doesn't use the (C) stack for much. Especially since the regex engine was change from recursive to iterative.

        Personally, I modify the header of my perl executables to reduce the per-thread stack allocation to a minimum (4k), and I've never encountered a problem with this. I don't know if this is possible with *nix executables.

        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]

In Section Seekers of Perl Wisdom