WatchDirectory Forum
watchDirectory forums >> Bug Reports >> CPU Pegged while FTPing?

Message started by toob on Oct 26th, 2006 at 6:22am

Title: CPU Pegged while FTPing?
Post by toob on Oct 26th, 2006 at 6:22am
Running Version of WDRun.  I just set WD to monitor directory to FTP .zip files (also created using WD).  While creating the .zip files it ran fine.  Now the .zip files are finished being created, but WDRun.exe is pulling up to 100% of my CPU now.  It is simply FTP'ing to the server.  I just turned up my fans to let this run tonight but I really don't like the idea of running it full bore for overnight?

I just stopped the task, and the proc. dropped right back down to 5% CPU.  I restarted the task, and was monitoring from my FTP client program, and do not see that it is uploading anymore files to the directory where it is supposed to upload.   Nope, I've confirmed that the task, while it claims to be monitoring, has stopped uploading via ftp, even though the history shows that it has connected to the FTP server. . . . what is it doing? When will it start uploading again?

I guess I'll stop the task for the night and just start uploading via my normal ftp method (manually), but it would be interesting to see if there is a solution to this.  

Also, concerning FTP via WD, it would be nice to monitor what files (i.e., where in the queue it is) are being uploaded and/or the upload rate (speed).  Not sure if this is too complicated but how will I know when it's done uploading?  I have over 3,000 files to upload. . . .


Title: Re: CPU Pegged while FTPing?
Post by Gert on Oct 27th, 2006 at 6:52am
Unfortunately, I was never able to reproduce this. A few other customers reported this issue, and one of them even let me use their userid/password to test against their FTP server, but it worked fine for me. It is probably related to other software running on the computer (winsock, firewall, something like that).


Title: Re: CPU Pegged while FTPing?
Post by toob on Oct 27th, 2006 at 7:24am
I run Win2k on an AMD 3200+XP machine with 2GB of memory.  When I started the process and was .zipping files, it ran just fine.  It only spiked the processor after it had been running the FTP for a while, and then I couldn't bring it back down without stopping the task.  The only task it has done this on for me so far is running the FTP to upload to my server. . . .

PS--I never was able to get it to start reading from that directory and pick back on the task reading existing files and uploading them to FTP  automatically.  There were all sorts of files (thousands) that it still hadn't uploaded, but I had to give up and simply FTP them using my FTP client.

Title: Re: CPU Pegged while FTPing?
Post by react on Mar 13th, 2007 at 8:07am

I know this is an old thread but I have some information that I hope will help diagnose it. I am able to repeatedly reproduce this behavior with a very basic watch folder -> FTP job in WD 4.2.0.

If I copy a file to my watch folder and wait for it to start transferring then copy another file in there while the transfer is still active the CPU utilization will jump to 100%. As soon as the first file finishes transferring and the second starts things return to normal. It is also worth nothing that the CPU spikes as soon as the second file is created, even though it is still being written to and should not have yet met the 'Wait for files... Until they are available (both methods)' requirement.

Please don't hesitate to contact me if I can be of any assistance with further testing.

Title: Re: CPU Pegged while FTPing?
Post by Gert on Mar 13th, 2007 at 5:59pm

I will check this out tomorrow to see if I can reproduce this.

Can you send me to the email in my signature (please ZIP it):

<task directory>\<yourtaskname>.config
<task directory>\<yourtaskname>\history.db

<task directory>: press CTRL+9 inside the watchDirectory Control Center to explore this directory
<yourtaskname>: the name of your task



Title: Re: CPU Pegged while FTPing?
Post by Gert on Mar 14th, 2007 at 10:03am
Thanks to Daniel ("react") I was finally able to reproduce this issue. Later today there will be a new Beta that will have this problem solved.


WatchDirectory Forum » Powered by YaBB 2.5.2!
YaBB Forum Software © 2000-2018. All Rights Reserved.