Re: GUI in Perl/Tk runs slow unless threads sleep periodically

if (my $key = $Queue->dequeue_nb) {
[download]

Solution: avoid dequeue_nb() unless you have a reason to use it. Ie, something else useful to do if there is nothing in the Q.

As coded, (without the sleep), your thread will consume 100% of the processing time of 1 cpu. If you have as many (or more) of those threads as cores, they will be consuming all your cpu whenever they can, which will not only make your GUI thread sluggish, but your entire system. So don't do that.

Recast your queue processing loop as:

while( my $key = $Queue->dequeue ) {
    do_something();
}
[download]

And when there is something for your thread to do, it will wake up, do it and go back to sleep, consuming no cpu when there is nothing to do.

What errors are you hoping to trap with eval?

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.

Comment on Re: GUI in Perl/Tk runs slow unless threads sleep periodically Select or Download Code

Replies are listed 'Best First'.
Re^2: GUI in Perl/Tk runs slow unless threads sleep periodically by Smile-n-Nod (Initiate) on Mar 24, 2011 at 16:29 UTC
The errors I'm hoping to trap with eval are in the &do_something() function.	[reply]
Re^3: GUI in Perl/Tk runs slow unless threads sleep periodically by BrowserUk (Patriarch) on Mar 24, 2011 at 16:50 UTC
The errors I'm hoping to trap with eval are in the &do_something() function. Then wrap that function, not the rest. 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]


XP is just a number
	PerlMonks