Re^4: removing all threads..

in reply to Re^3: removing all threads..
in thread removing all threads..

but I've found it difficult to do in the past without Threads::Shared which has some serious limitations.

Hm. Seems simple enough to me?:

#! perl -slw
use strict;
use threads;
use threads::shared;

my $sem :shared;
sub tprint {
    lock $sem;
    print @_;
}

my $dieNow :shared = 0;
$SIG{INT} = sub {
    tprint 'sigint seen';
    $dieNow = 1;
    return;
};

sub thread {
    my $tid = threads->tid;
    my $delay = int rand 10;
    my $next = time + $delay;
    while( sleep 1 ) {
        last if $dieNow;
        redo unless time > $next;
        tprint "[$tid] ping";
        $next = time + $delay;
    }
    tprint "$tid] ending";
}

my @threads = map async( \&thread ), 1 .. 10;

sleep 1 until $dieNow;
$dieNow = 1;

$_->join for @threads;
[download]

Outputs:

C:\test>1007974
[3] ping
[9] ping
[1] ping
[3] ping
[2] ping
[4] ping
[3] ping
[1] ping
[9] ping
[5] ping
[3] ping
[6] ping
[10] ping
sigint seen
[3] ping
7] ending
2] ending
5] ending
8] ending
1] ending
9] ending
4] ending
6] ending
10] ending
3] ending
[download]

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

Comment on Re^4: removing all threads.. Select or Download Code

Replies are listed 'Best First'.
Re^5: removing all threads.. by Tommy (Chaplain) on Dec 10, 2012 at 22:24 UTC
browserUk++ I keenly (and painfully) remember getting segfault after segfault with threads::shared on distributed cluster of rhel 5 servers I had to work with about 6 months back. I eventually gave up and just used stock threads. The application was about 2K lines and I wasn't about to try to find out why threads::shared wouldn't work...everything looked fine, and I was following all the rules. What's more, I needed to share some very complex datastructures (I believe the real problem was exactly that, and it was an uncompromising requirement). I got around the segfaults by using a not-so-elegant fix (Storable::lock_store / Storable::lock_retrieve on a ramdisk). I'm not proud of that, but it worked and it's been running in production as a persistent service for worldwide venues going on several months now -- no memleaks, no segfaults, no problems. It had to be done to get it to work on the old rhel 5 platforms. I chocked it up to having a perl that was too old when the same code ran fine on my own servers which had the most recent stable perl. I made a mental note that in the future I would need to be more careful with threads::shared (or avoid it entirely) when writing code that might need to run on legacy servers. Just my own personal experience; YMMV I appreciate the time you took in coding that example for me. I don't take it lightly that you freely gave your own valuable time to do that. Thank you. -- Tommy `$ perl -MMIME::Base64 -e 'print decode_base64 "YWNlQHRvbW15YnV0bGVyLm1lCg=="'`	[reply] [d/l]
Re^6: removing all threads.. by BrowserUk (Patriarch) on Dec 10, 2012 at 23:30 UTC
I keenly (and painfully) remember getting segfault after segfault with threads::shared on distributed cluster of rhel 5 servers I had to work with about 6 months back. I eventually gave up and just used stock threads. The application was about 2K lines and I wasn't about to try to find out why threads::shared wouldn't work...everything looked fine, and I was following all the rules. Could you show me the faulting code; here or privately? 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]
Re^7: removing all threads.. by Tommy (Chaplain) on Dec 10, 2012 at 23:58 UTC
I'd love to! Unfortunately, it's proprietary, confidental. I would have loved to get peer review of the codebase, but that was forbidden also. Secret sauce. Maybe I can cobble together a separate example that fails in a similar way... ...You know, actually I can't. I couldn't ever reproduce the problem on anything but those old rhel machines and I don't have access to them anymore (that project is done). The threads::shared code worked on all my own servers. What I can do is share a sample (mock) marshalled datastructure "storable" that contains a datastructure which in all likelihood would have made the original code/server puke. The act of passing structs like the dummy storable I'll share with you is what made the segfaults happen. I'll need a few hours before I can get that. It might be as long as tomorrow. Maybe there's something to be learned here, which I would enjoy very much! -- Tommy `$ perl -MMIME::Base64 -e 'print decode_base64 "YWNlQHRvbW15YnV0bGVyLm1lCg=="'`	[reply] [d/l]
Re^7: removing all threads.. by Tommy (Chaplain) on Dec 11, 2012 at 14:47 UTC
Alrighty. I'll give you the URL to download the mock storable file. You can check it out at the cmd line like so: `perl -MData::Dumper -MStorable -e '$Data::Dumper::Indent = 1; $a = Storable::lock_retrieve("example.storable"); delete $a->{ $_ }->{data} for keys %$a; print Dumper $a;'` ...Of course you'll want to NOT delete the data keys permanently because they contain binary data that are pertinent to the original functionality. The rest I'll explain in CB, as I'd prefer the contents of the file and its structure to remain private. Many Thanks -- Tommy `$ perl -MMIME::Base64 -e 'print decode_base64 "YWNlQHRvbW15YnV0bGVyLm1lCg=="'`	[reply] [d/l] [select]
Re^8: removing all threads.. by BrowserUk (Patriarch) on Dec 11, 2012 at 18:04 UTC
Re^9: removing all threads.. by Tommy (Chaplain) on Dec 12, 2012 at 04:44 UTC
Re^6: removing all threads.. by Tommy (Chaplain) on Dec 10, 2012 at 22:31 UTC
Now that I think about it again...I could have used packed strings, or some other similar marshalling method and just shared a re-vivifiable-as-hashref scalar string. Sigh -- Tommy `$ perl -MMIME::Base64 -e 'print decode_base64 "YWNlQHRvbW15YnV0bGVyLm1lCg=="'`	[reply] [d/l]

In Section Seekers of Perl Wisdom