On 7 July 2015 at 16:41, Akshay Mohit wrote:
> As I told earlier there is a code already written on Performance testing
> using Perl threads and I need to maintain and own it because the person who
> was doing it earlier left the organization, so I am bound to maintain the
> code which is using th
As I told earlier there is a code already written on Performance testing
using Perl threads and I need to maintain and own it because the person who
was doing it earlier left the organization, so I am bound to maintain the
code which is using threads and presently cant make use of any other
concept
On 7 July 2015 at 16:14, Akshay Mohit wrote:
> I need to maintain a code for performance testing which is fully written
> using Threads
That doesn't seem to help me a lot.
Because "Performance testing" in itself doesn't require threads. If
you just need to load up processors, then forks will do
Thanks Kent for the Quick reply.
I need to maintain a code for performance testing which is fully written
using Threads and I have no clue of the concepts so I wanted some stuffs
for it.
-Akshay
On Tue, Jul 7, 2015 at 9:34 AM, Kent Fredric wrote:
> On 7 July 2015 at 15:57, Akshay Mohit wrote:
On 7 July 2015 at 15:57, Akshay Mohit wrote:
> I am not so experienced in Perl and got a task to do in Threads.
The first question you have to ask is "Why do you need threads". What
are you doing?
Many people go "I need some sort of parallel process" and go "that
needs threads!".
But that is n
Tim Johnson wrote:
Can anyone give me a quick hint as to where to find documentation on how
to use threads w/Perl?
CPAN is best to start off with -- that way you develop better questions =)
http://search.cpan.org/search?query=Threads&mode=all
-Bill-
__Sx___
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
zentara
Sent: Thursday, January 22, 2004 9:11 PM
To: [EMAIL PROTECTED]
Subject: Re: threads in perl
On Thu, 22 Jan 2004 08:22:04 +0200, [EMAIL PROTECTED] (Igor
Ryaboy) wrote:
>Hi,
>Thanks for your help, 1
Igor Ryaboy wrote:
> Hi,
> Thanks for your help, 1 more question related to your advice
> Ok, How can I kill exec after it was started in different thread?
> Igor
>
when you fork, you have the pid of the child process. when you exec, the
program in exec will replaced the child process but the p
Hi,
Thanks for your help, 1 more question related to your advice
Ok, How can I kill exec after it was started in different thread?
Igor
-Original Message-
From: david [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 8:10 PM
To: [EMAIL PROTECTED]
Subject: RE: threads in perl
Igor Ryaboy wrote:
> I have no problem to alarm when timeout occurs in specific thread, I have
> a difficulty to abort a "system" command in that thread.
in that case, fork a different process in your thread, replace system with
exec and use the pid of the newly created process to abort itself w
I have no problem to alarm when timeout occurs in specific thread, I have a difficulty
to abort a "system" command in that thread.
-Original Message-
From: david [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 9:14 PM
To: [EMAIL PROTECTED]
Subject: RE: threads in p
Igor Ryaboy wrote:
> Hi,
> I have a thread that invokes system("command") that may stuck. I can't let
> this thread die because it may take a lot of time. Example:
>
> threads->new(\&srun);
> ..
> ..
> sub srun {
> system("");
> threads->self->join;
> }
> I need to kill the system command i
d if it takes more than define timeout.
Thanks,
Igor
-Original Message-
From: david [mailto:[EMAIL PROTECTED]
Sent: Monday, January 19, 2004 9:15 PM
To: [EMAIL PROTECTED]
Subject: RE: threads in perl
Igor Ryaboy wrote:
> Hi
> I want to kill a specific thread and thread->list to be u
IL PROTECTED]
> Subject: RE: threads in perl
>
> Igor Ryaboy wrote:
> > Hi
> > I want to kill a specific thread and thread->list to be updated (Like
> > thread->join but without waiting). Igor
>
> instead of killing a thread, why not just let the thread die
Hi,
Thanks for your tips,
Where can I get those modules?
Igor
-Original Message-
From: david [mailto:[EMAIL PROTECTED]
Sent: Monday, January 19, 2004 9:15 PM
To: [EMAIL PROTECTED]
Subject: RE: threads in perl
Igor Ryaboy wrote:
> Hi
> I want to kill a specific thread and thread
Igor Ryaboy wrote:
> Hi
> I want to kill a specific thread and thread->list to be updated (Like
> thread->join but without waiting). Igor
>
instead of killing a thread, why not just let the thread die when you need
to kill it? take a look at Thread::Exit and Thread::Suspend, they let you
kill
Hi
I want to kill a specific thread and thread->list to be updated (Like thread->join but
without waiting).
Igor
-Original Message-
From: david [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 9:15 PM
To: [EMAIL PROTECTED]
Subject: RE: threads in perl
Igor Ryaboy
Igor Ryaboy wrote:
> Hi,
> (Please ignore the previous mail.)
> In this example this fellow detaches all useless threads. In my case this
> is not an option , because a detached thread never ends.
this is plain wrong.
> For correct thread managing it is enough to remove the detached thread
> fr
to kill the process! (Verilog simulation in my case)
Thanks,
Igor
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of zentara
Sent: Wednesday, January 14, 2004 5:28 PM
To: [EMAIL PROTECTED]
Subject: Re: threads in perl
On Tue, 13 Jan 2004 17:17:20 +0200, [EMAIL
Hi,
The program is still exits sometimes without waiting for the threads to finish . I
can't understand it. It seem like the "join" just doesn't waits to the process to
finish , it just cleans after the thread and decrements the threads->list.
Igor
-Original Message-
From: zentara [mailt
On Sun, Oct 12, 2003 at 05:35:21PM +0200, Kevin Pfeiffer wrote:
> In article <[EMAIL PROTECTED]>, Zentara wrote:
> > [EMAIL PROTECTED] (Igor Ryaboy) wrote:
> >
> > foreach (@kiddies){ $_->join(); }
>
> Printing these out (i.e.):
> foreach (@kiddies){
> $_->join();
> print "$_ joined.\n";
>
In article <[EMAIL PROTECTED]>, Kevin Pfeiffer wrote:
[...]
> What does the last line do. I looked at man threads:
> $thread->join
>This will wait for the corresponding thread to join. When the
>thread finishes, join() will return the return values of
>the entry
In article <[EMAIL PROTECTED]>, Zentara wrote:
> On Sun, 12 Oct 2003 08:24:52 +0200, [EMAIL PROTECTED] (Igor
> Ryaboy) wrote:
[...]
> Bear in mind I'm not a "threading expert", just a hacker with ideas. :-)
> Here is a snippet to try. I used a global for $param instead of passing
> it, but you may
; in some way?
THANKS A LOT
Igor
-Original Message-
From: zentara [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 7:44 PM
To: [EMAIL PROTECTED]
Subject: Re: threads in perl
On Wed, 8 Oct 2003 13:13:13 +0200, [EMAIL PROTECTED] (Igor
Ryaboy) wrote:
>Hi,
>I need help in s
2 3:29 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: threads in perl
>
>
> On Wed, 2002-07-24 at 02:57, [EMAIL PROTECTED] wrote:
> > Hello All,
> >
> > I want to execute same perl procedure with different parameters at
> > the almost
On Wed, 2002-07-24 at 02:57, [EMAIL PROTECTED] wrote:
> Hello All,
>
> I want to execute same perl procedure with different parameters at
> the almost same time in a perl program indefendantly. (next process
> should be started without waiting for the end of previous one) The
> procedure is l
rohana wrote at Wed, 24 Jul 2002 08:57:17 +0200:
> I want to execute same perl procedure with different parameters at the almost same
>time in a perl
> program indefendantly. (next process should be started without waiting for the end
>of previous
> one) The procedure is located in .pm file. H
perldoc thread
This turned up a library on how to thread processes in perl.
Seemed fairly straightforward. (though it did say it was
experimental, so there may be a better module out there?)
-Tony
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday,
28 matches
Mail list logo
