note
Anonymous Monk
<P><I>Any hint why running as scheduled has such a terrible effect on performance?</i>
<P>Seems to me the emulation/virtualization is slowing things down, I have no idea why, probably due to the design or a bug :/
<P>Last time I noticed slower performance than I expected, I was printing/logging lots to STDOUT, which cmd.exe was really slow to show, slower than database access
<P>Running with wperl.exe or redirecting STDOUT to a file <C> >log.txt</C> sped up the process more than double, maybe you can try that?
<P>Another thing I've seen is if your video driver doesn't load, but the generic one gets loaded, the whole computer screeches to a snails pace -- check the logs, maybe they'll have some things :)
<P>Does your scheduled process launch a child, or do you do your work in the main process?
<P>Maybe all scheduled tasks are throttled, but children they launch aren't -- you could try launching a detached child ( [cpan://Proc::Background] )
<P>IIRC scheduled tasks used to be limited to ~60-90min runtime
<P>You could also try increasing the priority
<P>I doubt this is perl-specific, I think you'll have better luck on a MSDN/WMWare support forum :/
<P>Good luck
940786
940786
14