Dearperl-win32-users，
Best Regards!
wenyan N.
[EMAIL PROTECTED]
2004-12-07 09:36:27 Beijing time
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/my
Laurent Duperval wrote:
It looks like the issue is at the Perl level. Whenever I run a script
(for example, the PPM script), the CPU run amok. When I launch PPM, it
takes 10-15 seconds before I get the prompt.
are you maybe running a virus scanner? that is scanning every file access?
willem
___
On Mon, 6 Dec 2004 14:56:10 -0500, henry <[EMAIL PROTECTED]> wrote:
>
>
> I don't think 1 GB RAM is enough for all the things you have running on it.
> How's your memory utilization?
>
I have about 800 MB free. There's very little activity on the machine.
L
___
I don't think 1 GB RAM is enough for all the things you have running on it. How's your memory utilization?
-Henry
From: Laurent DupervalSent: Mon 12/6/2004 2:34 PMTo: [EMAIL PROTECTED]Subject: Re: Atrocious performance on W2K PIII
On Mon, 6 Dec 2004 12:05:57 -0700, [EMAIL PROTECTED] <[EMA
On Mon, 6 Dec 2004 12:05:57 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Have you tried a cleanboot?
> Grab the msconfig install from Microsoft for
> Win2k, and disable anything not neccessary to run/operate the test.
> (including security software like antivirus, firewalls, etc). If you
Have you tried a cleanboot? Grab the msconfig install from Microsoft for
Win2k, and disable anything not neccessary to run/operate the test.
(including security software like antivirus, firewalls, etc). If you the
issue goes away in a cleanboot, gradually readd services/startup items and
keep
Hi,
I'm trying to install Bugzilla on a Windows 2000 system. Any time I
try to access a Web page, the CPU goes through the roof. It hovers
around 95-100% before the page is displayed.
It looks like the issue is at the Perl level. Whenever I run a script
(for example, the PPM script), the CPU run
Try writing it as a service using Win32::Daemon (http://www.roth.net/perl),
then using Windows' auto-restart functionality. If it runs in a service context
it won't be killable in Task Manager anyway (although the TerminateProcess API
still works so pskill.exe from sysinternals and other similar
