Appalling Dreamweaver performance

I use Dreamweaver as my editor, mainly because I'm familiar with it, although I only use
about 1% of its capabilities. However it generally handles long files well. The other day
I downloaded the two shortest of Brian Dunning's sets of test data *. I opened the
shortest in Dreamweaver, had a quick look at it, and realised I would have to replace the
quote, comma, quote separators with semicolons, as part of converting the files to my
format.

So I thought I would do that while I was working out what else I had to do. I entered the
old separator and the replacement in the 'Find and replace' window, then hit 'Replace
all', expecting the job be done in a few seconds. First I thought nothing was happening,
but then I realised it was trudging through the file, as if it was wading through waist
high molasses.

So I closed the results window, and opened another file, but a few seconds later focus
switched back to the original file. I tried a couple of times more, but each time it
returned to the original window. I watched in morbid fascination for a bit, then decided I
would let it go, just to see how long it took.

The file contained 500 lines, and was about 80 K. It was taking five seconds to process
each line, and eventually finished in about 40 minutes.

The problem appeared to be the results processing. I have only looked at the results list
about twice, out of idle curiosity, but never saw any thing that I thought could be
remotely useful. I would like to be able to turn results logging off altogether, as it
wastes real estate (and time!), but this appears to be impossible.

On this occasion the program was apparently writing a new line every time it replaced a
separator (9 times in each line), and then when it finished processing a line it would
erase all the intermediate result lines, and write a new one for the whole line. At the
same time it reopened the results window if I had closed it, and return focus to the file
being processed.

I then wrote a PHP program to read the file, split it, clean up and re-arrange the various
elements, enter them into an array in my format, and finally save it as a file my program
could handle.

After I had got this running on the 500 line file I used it to process the 5000 line
file. The whole process was done in the blink of an eye -- literally a fraction of a
second.


* http://www.briandunning.com/sample-data/


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Appalling Dreamweaver performance

--=-kvO4A0BzzeBY74ElJ/Iv
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Mon, 2010-02-01 at 11:28 +1100, clancy_1@cybec.com.au wrote:

> I use Dreamweaver as my editor, mainly because I'm familiar with it, although I only use
> about 1% of its capabilities. However it generally handles long files well. The other day
> I downloaded the two shortest of Brian Dunning's sets of test data *. I opened the
> shortest in Dreamweaver, had a quick look at it, and realised I would have to replace the
> quote, comma, quote separators with semicolons, as part of converting the files to my
> format.
>
> So I thought I would do that while I was working out what else I had to do. I entered the
> old separator and the replacement in the 'Find and replace' window, then hit 'Replace
> all', expecting the job be done in a few seconds. First I thought nothing was happening,
> but then I realised it was trudging through the file, as if it was wading through waist
> high molasses.
>
> So I closed the results window, and opened another file, but a few seconds later focus
> switched back to the original file. I tried a couple of times more, but each time it
> returned to the original window. I watched in morbid fascination for a bit, then decided I
> would let it go, just to see how long it took.
>
> The file contained 500 lines, and was about 80 K. It was taking five seconds to process
> each line, and eventually finished in about 40 minutes.
>
> The problem appeared to be the results processing. I have only looked at the results list
> about twice, out of idle curiosity, but never saw any thing that I thought could be
> remotely useful. I would like to be able to turn results logging off altogether, as it
> wastes real estate (and time!), but this appears to be impossible.
>
> On this occasion the program was apparently writing a new line every time it replaced a
> separator (9 times in each line), and then when it finished processing a line it would
> erase all the intermediate result lines, and write a new one for the whole line. At the
> same time it reopened the results window if I had closed it, and return focus to the file
> being processed.
>
> I then wrote a PHP program to read the file, split it, clean up and re-arrange the various
> elements, enter them into an array in my format, and finally save it as a file my program
> could handle.
>
> After I had got this running on the 500 line file I used it to process the 5000 line
> file. The whole process was done in the blink of an eye -- literally a fraction of a
> second.
>
>
> * http://www.briandunning.com/sample-data/
>
>


Don't use Dreamweaver then :p

Joking aside (Dreamweaver is a very capable editor, although it is quite
large for simple find and replace tasks) how were you performing the
find and replace? Regular expression replacements will be much slower,
although it shouldn't account for quite the speed hit you saw. For
simple tasks like that, I'd recommend Notepad++. It has code
highlighting and folding, regex find/replace features, and a slew of
other bits that make it a very good editor, and it's very speedy to
boot.

Thanks,
Ash
http://www.ashleysheridan.co.uk



--=-kvO4A0BzzeBY74ElJ/Iv--

Re: Appalling Dreamweaver performance

On 1 February 2010 00:28, wrote:
>
> I use Dreamweaver as my editor, mainly because I'm familiar with it, alth=
ough I only use
> about 1% of its capabilities. However it generally handles long files wel=
l.  The other day
> I downloaded the two shortest of Brian Dunning's sets of test data *. =C2=
=A0I opened the
> shortest in Dreamweaver, had a quick look at it, and realised I would hav=
e to replace the
> quote, comma, quote separators with semicolons, as part of converting the=
files to my
> format.
>
> So I thought I would do that while I was working out what else I had to d=
o. I entered the
> old separator and the replacement in the 'Find and replace' window, then =
hit 'Replace
> all', expecting the job be done in a few seconds. First I thought nothing=
was happening,
> but then I realised it was trudging through the file, as if it was wading=
through waist
> high molasses.
>
> So I closed the results window, and opened another file, but a few second=
s later focus
> switched back to the original file. I tried a couple of times more, but e=
ach time it
> returned to the original window. I watched in morbid fascination for a bi=
t, then decided I
> would let it go, just to see how long it took.
>
> The file contained 500 lines, and was about 80 K. It was taking five seco=
nds to process
> each line, and eventually finished in about 40 minutes.
>
> The problem appeared to be the results processing. I have only looked at =
the results list
> about twice, out of idle curiosity, but never saw any thing that I though=
t could be
> remotely useful. I would like to be able to turn results logging off alto=
gether, as it
> wastes real estate (and time!), but this appears to be impossible.
>
> On this occasion the program was apparently writing a new line every time=
it replaced a
> separator (9 times in each line), and then when it finished processing a =
line it would
> erase all the intermediate result lines, and write a new one for the whol=
e line.  At the
> same time it reopened the results window if I had closed it, and return f=
ocus to the file
> being processed.
>
> I then wrote a PHP program to read the file, split it, clean up and re-ar=
range the various
> elements, enter them into an array in my format, and finally save it as a=
file my program
> could handle.
>
>  After I had got this running on the 500 line file I used it to proc=
ess the 5000 line
> file. The whole process was done in the blink of an eye -- literally a fr=
action of a
> second.
>
>
> * http://www.briandunning.com/sample-data/
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

And the moral of the story is "Be happy that you learnt PHP!".


--=20
-----
Richard Quadling
"Standing on the shoulders of some very clever giants!"
EE : http://www.experts-exchange.com/M_248814.html
EE4Free : http://www.experts-exchange.com/becomeAnExpert.jsp
Zend Certified Engineer : http://zend.com/zce.php?c=3DZEND002498&r=3D213474=
731
ZOPA : http://uk.zopa.com/member/RQuadling

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Appalling Dreamweaver performance

--00504502cb2b7f1e49047e7f88e4
Content-Type: text/plain; charset=ISO-8859-1

Notepad++ also has session saving capabilities. This means you can save
which files you're working on, close Notepad++, and reload those files at a
later date. It's cool.

On Sun, Jan 31, 2010 at 4:51 PM, Ashley Sheridan
wrote:

> On Mon, 2010-02-01 at 11:28 +1100, clancy_1@cybec.com.au wrote:
>
> > I use Dreamweaver as my editor, mainly because I'm familiar with it,
> although I only use
> > about 1% of its capabilities. However it generally handles long files
> well. The other day
> > I downloaded the two shortest of Brian Dunning's sets of test data *. I
> opened the
> > shortest in Dreamweaver, had a quick look at it, and realised I would
> have to replace the
> > quote, comma, quote separators with semicolons, as part of converting the
> files to my
> > format.
> >
> > So I thought I would do that while I was working out what else I had to
> do. I entered the
> > old separator and the replacement in the 'Find and replace' window, then
> hit 'Replace
> > all', expecting the job be done in a few seconds. First I thought nothing
> was happening,
> > but then I realised it was trudging through the file, as if it was wading
> through waist
> > high molasses.
> >
> > So I closed the results window, and opened another file, but a few
> seconds later focus
> > switched back to the original file. I tried a couple of times more, but
> each time it
> > returned to the original window. I watched in morbid fascination for a
> bit, then decided I
> > would let it go, just to see how long it took.
> >
> > The file contained 500 lines, and was about 80 K. It was taking five
> seconds to process
> > each line, and eventually finished in about 40 minutes.
> >
> > The problem appeared to be the results processing. I have only looked at
> the results list
> > about twice, out of idle curiosity, but never saw any thing that I
> thought could be
> > remotely useful. I would like to be able to turn results logging off
> altogether, as it
> > wastes real estate (and time!), but this appears to be impossible.
> >
> > On this occasion the program was apparently writing a new line every time
> it replaced a
> > separator (9 times in each line), and then when it finished processing a
> line it would
> > erase all the intermediate result lines, and write a new one for the
> whole line. At the
> > same time it reopened the results window if I had closed it, and return
> focus to the file
> > being processed.
> >
> > I then wrote a PHP program to read the file, split it, clean up and
> re-arrange the various
> > elements, enter them into an array in my format, and finally save it as a
> file my program
> > could handle.
> >
> > After I had got this running on the 500 line file I used it to process
> the 5000 line
> > file. The whole process was done in the blink of an eye -- literally a
> fraction of a
> > second.
> >
> >
> > * http://www.briandunning.com/sample-data/
> >
> >
>
>
> Don't use Dreamweaver then :p
>
> Joking aside (Dreamweaver is a very capable editor, although it is quite
> large for simple find and replace tasks) how were you performing the
> find and replace? Regular expression replacements will be much slower,
> although it shouldn't account for quite the speed hit you saw. For
> simple tasks like that, I'd recommend Notepad++. It has code
> highlighting and folding, regex find/replace features, and a slew of
> other bits that make it a very good editor, and it's very speedy to
> boot.
>
> Thanks,
> Ash
> http://www.ashleysheridan.co.uk
>
>
>

--00504502cb2b7f1e49047e7f88e4--

Re: Appalling Dreamweaver performance

--001636c5b63e841c2d047e80ec9c
Content-Type: text/plain; charset=ISO-8859-1

Dreamweaver is notorious for memory leaks (some releases have much more
severe issues than others.) Sometimes just closing the app and then
reopening makes a big difference, especially when it comes to tasks that
take a large amount of memory. That said, I'm certainly not sure this was
the issue, but I pointed it out just in case it was contributing to your
pain.

Adam

On Sun, Jan 31, 2010 at 8:02 PM, Allen McCabe wrote:

> Notepad++ also has session saving capabilities. This means you can save
> which files you're working on, close Notepad++, and reload those files at a
> later date. It's cool.
>
> On Sun, Jan 31, 2010 at 4:51 PM, Ashley Sheridan
> wrote:
>
> > On Mon, 2010-02-01 at 11:28 +1100, clancy_1@cybec.com.au wrote:
> >
> > > I use Dreamweaver as my editor, mainly because I'm familiar with it,
> > although I only use
> > > about 1% of its capabilities. However it generally handles long files
> > well. The other day
> > > I downloaded the two shortest of Brian Dunning's sets of test data *.
> I
> > opened the
> > > shortest in Dreamweaver, had a quick look at it, and realised I would
> > have to replace the
> > > quote, comma, quote separators with semicolons, as part of converting
> the
> > files to my
> > > format.
> > >
> > > So I thought I would do that while I was working out what else I had to
> > do. I entered the
> > > old separator and the replacement in the 'Find and replace' window,
> then
> > hit 'Replace
> > > all', expecting the job be done in a few seconds. First I thought
> nothing
> > was happening,
> > > but then I realised it was trudging through the file, as if it was
> wading
> > through waist
> > > high molasses.
> > >
> > > So I closed the results window, and opened another file, but a few
> > seconds later focus
> > > switched back to the original file. I tried a couple of times more, but
> > each time it
> > > returned to the original window. I watched in morbid fascination for a
> > bit, then decided I
> > > would let it go, just to see how long it took.
> > >
> > > The file contained 500 lines, and was about 80 K. It was taking five
> > seconds to process
> > > each line, and eventually finished in about 40 minutes.
> > >
> > > The problem appeared to be the results processing. I have only looked
> at
> > the results list
> > > about twice, out of idle curiosity, but never saw any thing that I
> > thought could be
> > > remotely useful. I would like to be able to turn results logging off
> > altogether, as it
> > > wastes real estate (and time!), but this appears to be impossible.
> > >
> > > On this occasion the program was apparently writing a new line every
> time
> > it replaced a
> > > separator (9 times in each line), and then when it finished processing
> a
> > line it would
> > > erase all the intermediate result lines, and write a new one for the
> > whole line. At the
> > > same time it reopened the results window if I had closed it, and return
> > focus to the file
> > > being processed.
> > >
> > > I then wrote a PHP program to read the file, split it, clean up and
> > re-arrange the various
> > > elements, enter them into an array in my format, and finally save it as
> a
> > file my program
> > > could handle.
> > >
> > > After I had got this running on the 500 line file I used it to process
> > the 5000 line
> > > file. The whole process was done in the blink of an eye -- literally a
> > fraction of a
> > > second.
> > >
> > >
> > > * http://www.briandunning.com/sample-data/
> > >
> > >
> >
> >
> > Don't use Dreamweaver then :p
> >
> > Joking aside (Dreamweaver is a very capable editor, although it is quite
> > large for simple find and replace tasks) how were you performing the
> > find and replace? Regular expression replacements will be much slower,
> > although it shouldn't account for quite the speed hit you saw. For
> > simple tasks like that, I'd recommend Notepad++. It has code
> > highlighting and folding, regex find/replace features, and a slew of
> > other bits that make it a very good editor, and it's very speedy to
> > boot.
> >
> > Thanks,
> > Ash
> > http://www.ashleysheridan.co.uk
> >
> >
> >
>



--
Nephtali: PHP web framework that functions beautifully
http://nephtaliproject.com

--001636c5b63e841c2d047e80ec9c--

Re: Appalling Dreamweaver performance

On Mon, 01 Feb 2010 00:51:39 +0000, ash@ashleysheridan.co.uk (Ashley Sheridan) wrote:

>On Mon, 2010-02-01 at 11:28 +1100, clancy_1@cybec.com.au wrote:
..............................
>
>Don't use Dreamweaver then :p
>
>Joking aside (Dreamweaver is a very capable editor, although it is quite
>large for simple find and replace tasks) how were you performing the
>find and replace? Regular expression replacements will be much slower,
>although it shouldn't account for quite the speed hit you saw. For
>simple tasks like that, I'd recommend Notepad++. It has code
>highlighting and folding, regex find/replace features, and a slew of
>other bits that make it a very good editor, and it's very speedy to
>boot.

I was doing a simple replace: "," with ; As I mentioned, I use Dreamweaver both its
editing and its file managing capabilities, and as I spend a lot of time programming it is
nearly always open, so it gets used for odd jobs like this (which it usually does very
well).

However there is definitely something seriously wrong with its implementation of this
feature. After reading some of the other comments I thought I should try the same thing
again this morning, while the computer was fresh. I did the same job on the same file. The
screen was refreshed after each line was completely processed, and for the first few lines
the cursor ran quite quickly down the screen. But by line 130 it had slowed to about 1line
per second, and last time by the end it was taking more than five seconds to do each line.

I didn't bother to let it run to completion, but I did look at the results log. This had a
new line for every replacement-- 10 lines of log for each line of the original file. I
expect this is the explanation for the initial slow performance but I can't understand
what they have done to make it slow down as it progresses -- unless they start searching
again at the beginning of the file after each replacement? Given the cumbersome error
logging this is just conceivable.

I have had it crash once or twice after I have opened a lot of files (usually after I have
searched the whole folder for every reference to a variable a number of times), but
generally I have found quite reliable.

One feature which I find really annoying is that if you tell it to search a folder for a
particular variable name, it doesn't seem to be possible to tell it to only search certain
directories, and certain file extensions. If Notepad++ offered this feature I would
certainly be tempted to try it.


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: Appalling Dreamweaver performance

--0016e64dc9a64d1b39047ee190fc
Content-Type: text/plain; charset=ISO-8859-1

Try the NetBeans then

--0016e64dc9a64d1b39047ee190fc--

Re: Appalling Dreamweaver performance

--0016e6d9a3a2cb7ec7047ee24643
Content-Type: text/plain; charset=UTF-8

On Fri, Feb 5, 2010 at 3:59 PM, Lenin wrote:

> Try the NetBeans then
>

Personally, I've found that Programmer's Notepad 2 is a pretty capable
editor, and has some nice features such as auto-closing elements when
working with markup languages (HTML, XML, XSL, XHTML, etc.).

http://www.pnotepad.org


// Todd

--0016e6d9a3a2cb7ec7047ee24643--