Without sight of the modified script, plus the bat files, I could only guess. A word of caution though, if your not already using 5.8.4 or 5.8.5, upgrade before continuing. Many early bugs in ithreads where fixed in these builds. There is no point in re-discovering them:)
I don't seem to be getting those warnings. Any ideas?
No!?
use Benchmark qw[ timethis ]; timethis( 10, sub { my $x = 'A' <=> 'B' } ); Argument "B" isn't numeric in numeric comparison (<=>) at (eval 12) li +ne 1. Argument "A" isn't numeric in numeric comparison (<=>) at (eval 12) li +ne 1. timethis 10: 0 wallclock secs ( 0.00 usr + 0.00 sys = 0.00 CPU) (warning: too few iterations for a reliable count)
... and we're trying to profile part of our software so that we can make accurate...
I can only re-emphasis. "Timing" + "threads" !== "accurate". In fact, it will not even be consistant. This is not an error (of threads or Perl's ithreads), it's just a fact of life with preemptive multi-processing.
With the additional information, and another look at your script, it looks like your trying to simulate a server environment and draw conclusions based upon that simulation. This will not work. Your simulation is simply not accurate, nor representative enough to be of any merit.
If you need to profile, then you should be using a real profiler on the real code in the real environment, or as close to it as is possible to achieve.
That's a pretty flat judgement based on very little information, so don't be offended. You may know what your doing is good enough for your purpose--it just doesn't look like it from where I am sitting :)
In reply to Re^3: "Thread already joined at..." and "A thread exited while x threads were running" errors
by BrowserUk
in thread "Thread already joined at..." and "A thread exited while x threads were running" errors
by nickos
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |