DW FTP is slow and causes CPU Spike

Question

Does anyone know why DW causes the CPU to jump up when it is
performing FTP operations? I'm new to DW and maybe this is normal,
but it shouldn't be. When I perfrom FTP activities, DW usually
takes up about 60-70% of the CPU???
Also, why is the FTP client so slow?
Dreamweaver takes so much longer than other FTP clients. I
compared it's usage to SmartFTP, FileZilla, and Windows built in
FTP, and Dreamweaver is so slow on a magnitude of 20x - 30x. For a
quick test I tried to pull down a directory using dreamweaver. I
have all the files local already, so I told DW not to overwrite the
files...so you would think it should speed through all the files
and realize that they are all dups and not download anything, for a
directory with 15 files in it, i would think this FTP operation
should take about 2 seconds. but it takes dreamweaver about 4
minutes to complete this, all my other FTP clients can figure this
out in under 5 seconds, and they don't need to spike the CPU to do
it.
A quick search on the web tells me that I am not the only
person with these problems.
I really hope Adobe plans on fixing the FTP problems.
Technical details:
Dreamweaver CS3.
Windows Vista SP1, 4GB ram, Fujitsu T4220

Answer 1

I've had a related, ongoing problem with CS3 running up the
CPU and acting
slow for just about every operation for no apparent reason.
It goes in
surges, and just acts like molasses half the time, very
annoying. It is to
the point that I really don't use CS3, I use DW8, but try to
use CS3 here
and again to see if it has started working or if there is
some patch
released. This is on my XP workstation at work, and my Vista
workstation at
home. Both systems run CS3 slow enough that I just don't use
CS3. This has
been going on for over a year, since I got my copy of CS3.
Too bad really, because I am tasked with approving CS3 for
use by the rest
of our WEB team and I haven't been able to do that, so we
continue to use
DW8. We are missing out on Spry integration and are slowly
switching over
to Eclipse and Aptana instead. I think that if the CPU bug
isn't fixed, CS3
will be the version that has us switch away entirely. The
only hope seems to
be if they release the next version of DW before we can
completely switch
away. We are a smallish state agency and only have 8 DW
licenses, but
that's seven licenses they missed out on the upgrade path
with unless this
is fixed (mine is the only upgraded so far). It just isn't
useable in its
present state. :-\
"HenryHill" <[email protected]> wrote in
message
news:[email protected]...
> This has been a problem with Dreamweaver for a while
now. I would have
> thought
> that Adobe would have fixed the FTP issues, or at least
improved upon them
> by
> now.
>
> One of the things you can try is to disable the
"Maintain synchronization
> information" checkbox in the "Remote Info" section of a
site definition.
> although, you won't get the benefit of synchronization
in Dreamweaver, but
> you
> will get speed improvements, and your computer's CPU
won't spike and sound
> like
> a jumbo jet taking off every time you perform a FTP
operation.
>
> You can also try submitting a bug report as "John T
Smith" recommended,
> but I
> can pretty much guarantee you it won't do any good. We
have submitted
> many
> reports over the years and never heard anything.
>
> Your best bet is to go with an external FTP client such
as FileZilla
> (free!).
> You get the benefit of multiple connections so your
uploads/downloads are
> faster, plus it gives you a lot more feedback as the
FTPing is occuring,
> such
> as transfer speed, how many files have transfered, how
many are left, any
> errors. it will also auto detect if passive FTP is
needed, you can pause,
> stop, restart, it also shows you the exact ftp commands
that it is sending
> and
> what the responses are from the server. These are things
that Adobe
> should
> have included in the FTP client. As far as most of us
are concerned, the
> FTP
> client built into Dreamweaver is in the dark ages
compared to modern day
> FTP
> clients.
>
> Their are a lot of benefits to the built in client, but
for us, the
> negatives
> out weigh the positives.
>
>
>