Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re^5: A new CB reader

by marioroy (Vicar)
on Jul 11, 2019 at 01:32 UTC ( #11102657=note: print w/replies, xml ) Need Help??

in reply to Re^4: A new CB reader
in thread A new CB reader

Here is the smaller diff output (short form) for using MCE::Child and MCE::Channel. There is no involvment of the separate shared-manager process or thread due to not using MCE::Shared.

diff -r pm-cb-master/lib/PM/CB/ pm-cb-master2/lib/PM/CB/Cont 17a18,20 > if ($INC{''}) { > $SIG{QUIT} = sub { threads->exit }; > } 45,47c48,52 < $self->{to_comm}->insert(0, ['quit']); < $self->{communicate_t}->join; < $self->{to_gui}->insert(0, ['quit']); --- > if ($^O ne 'MSWin32' || ! $INC{'MCE/'}) { > $self->{communicate_t}->kill('QUIT'); > $self->{communicate_t}->join; > } > $self->{to_gui}->enqueue(['quit']); diff -r pm-cb-master/lib/PM/CB/ pm-cb-master2/lib/PM/CB/ 676c676 < $self->{to_control}->insert(0, ['quit']); --- > $self->{to_control}->enqueue(['quit']); diff -r pm-cb-master/pm-cb-g pm-cb-master2/pm-cb-g 58,59c58,59 < use if $mce => 'MCE::Hobo'; < use if $mce => 'MCE::Shared'; --- > use if $mce => 'MCE::Child'; > use if $mce => 'MCE::Channel'; 66c66 < ? ('MCE::Shared', 'queue', 'MCE::Hobo') --- > ? ('MCE::Channel', 'new', 'MCE::Child')

Regards, Mario

Replies are listed 'Best First'.
Re^6: A new CB reader
by Tux (Abbot) on Jul 12, 2019 at 15:18 UTC

    All of your changes have been merged to my fork of pm-cb, which supports config files ($HOME/pm-cb.rc, $HOME/.pm-cbrc and/or $HOME/.config/pm-cb)

    Enjoy, Have FUN! H.Merijn
      Thank you! I tried to integrate the changes in my way. Please verify it works on MSWin, too. Is the QUIT signal still needed? Using MCE::Child makes quitting a bit slower, as all the messages in the queue must be processed first, but otherwise, it should work the same way as the other options.

      map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

        Signal handling is not necessary. I did that due to MCE::Channel lacking the insert method. Ah, your branch adds an insert wrapper calling enqueue :). That's a clever way calling insert when available.

      Hi Tux,

      In truth, I never imagined for pm-cb-g to support both the -m and -M options. The reason I tested pm-cb-g using MCE::Child was for testing the 3 together Tk, MCE::Child, and MCE::Channel on Windows, Linux, and macOS.

      Using MCE::Hobo / MCE::Shared. Notice the extra shared-manager process.

      $ ps -e | grep perl 68028 ttys001 0:00.32 perl -I../test_mce pm-cb-g -m # main process 68029 ttys001 0:00.01 perl -I../test_mce pm-cb-g -m # shared mgr 68030 ttys001 0:00.01 perl -I../test_mce pm-cb-g -m # control 68031 ttys001 0:00.09 perl -I../test_mce pm-cb-g -m # communicate

      Using MCE::Child / MCE::Channel.

      $ ps -e | grep perl 68035 ttys001 0:00.29 perl -I../test_mce pm-cb-g -M # main process 68036 ttys001 0:00.01 perl -I../test_mce pm-cb-g -M # control 68037 ttys001 0:00.09 perl -I../test_mce pm-cb-g -M # communicate


      Q. Why was MCE::Hobo created?

      A. At the time, I wanted a threads-like parallel module to be included with MCE::Shared. It was also helpful for intense testing of MCE::Shared.

      Q. Why did I create MCE::Child years later?

      A. Well, MCE::Channel is new and included with MCE 1.841. I needed something to complement it including running on Perl 5.8. So, I tried making another threads-like parallel module. MCE::Child uses a common MCE::Channel object for IPC versus IPC handled by the shared-manager process. After several attempts, got it to work including running on the Windows platform.

      Q. Which one to choose?

      A. MCE::Child is lighter versus MCE::Hobo because not involving the shared-manager process. However, for apps that have shared variables (i.e. shared array, hash, scalar, etc.), then continue using MCE::Hobo. It's a moot point if the shared-manger is already running.

      Q. What about MCE::Channel->new versus MCE::Shared->queue?

      A. MCE::Channel involves no manager process and behaves very much like a pipe. It eliminates any concerns for Producer(s) running faster than Consumers. For MCE::Shared, items appended to a shared queue are sent to the shared-manager process where the data resides (i.e. in memory). This means the possibility for Producer(s) to run faster than Consumers. But no worries, MCE::Shared::Queue includes the await method for throttling if ever needed.

      Regards, Mario

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://11102657]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2019-11-12 10:50 GMT
Find Nodes?
    Voting Booth?
    Strict and warnings: which comes first?

    Results (65 votes). Check out past polls.