Topic: VEDIT Performance (1 of 5), Read 26 times
Conf: Installation, Configuration
From: Tom Merritt
Date: Wednesday, September 12, 2007 10:58 AM

I have VEDIT installed on a Dell Optiplex GX620 with a Pentium 4 processor (3.46 GHz), 504 MB of RAM, 75 GB hard drive, and running Windows XP Service Pack 2. I am opening a text file on the C: drive that is 568 MB in VEDIT. In navigating though the file and in doing text searching I'm noticing long wait periods with a "waiting on disk" message at the bottom. The waits are longer than I expected and perhaps several minutes in duration. Is this normal and is there anything I can do to speed things up? Task manager indicates that most of the memory is being utilized and the CPU is not pegged. In my experience XP doesn't run well with less than 1 GB of memory. Also, I closed all other desktop applications prior to the delay described above. Any suggestions welcomed. Thanks, Tom

 


Topic: Re: VEDIT Performance (2 of 5), Read 24 times
Conf: Installation, Configuration
From: Ted Green
Date: Wednesday, September 12, 2007 11:44 AM

At 11:00 AM 9/12/2007, you wrote:
>From: "Tom Merritt"
>
>I have VEDIT installed on a Dell Optiplex GX620 with a Pentium 4 processor (3.46 GHz), 504 MB of RAM, 75 GB hard drive, and running Windows XP Service Pack 2. I am opening a text file on the C: drive that is 568 MB in VEDIT. In navigating though the file and in doing text searching I'm noticing long wait periods with a "waiting on disk" message at the bottom. The waits are longer than I expected and perhaps several minutes in duration. Is this normal and is there anything I can do to speed things up? Task manager indicates that most of the memory is being utilized and the CPU is not pegged. In my experience XP doesn't run well with less than 1 GB of memory. Also, I closed all other desktop applications prior to the delay described above. Any suggestions welcomed. Thanks, Tom

VEDIT does not use more than 1M per open file; so adding memory does not help as VEDIT will not use it. Windows will use the additional memory as a disk cache, which will help.

We do suggest that when you reach the end of a huge (20Meg+) file, that instead of going to the beginning, that you close the file and re-open it. You can create a hot-key to do this; the close re-open time is nearly instantaneous. See this page for details:

http://vedit.com/huge_files.htm

Ted.

 


Topic: Re: VEDIT Performance (3 of 5), Read 27 times
Conf: Installation, Configuration
From: Pauli Lindgren
Date: Thursday, September 13, 2007 09:02 AM

On 9/12/2007 11:44:37 AM, Ted Green wrote:
>
> We do suggest that when you reach the end of a huge
> (20Meg+) file, that instead of going to the beginning, that
> you close the file and re-open it. You can create a hot-key
> to do this; the close re-open time is nearly instantaneous.

That only helps if you have not edited the file.
If the file has been changed, it will be saved, which takes more time than Ctrl-Home.
If the file is not to be edited, it is better to open it as Read Only.
This makes searches and moving around file much faster.

I tested the speed with a 440MB file (about 5.6 million lines).

I have Dell Precision 380 with Pentium 4 (around 3.1 GHz, IIRC).
However, it has 2GB of RAM, so there is lots of room for disk cache.

- Searching a text that is found only on the last line took 19 sec on the first try (although probably the file was partially in the cache already).
- Subsequent searches took 12 to 15 sec.
- Search reverse for text on first line: 50 sec.
- Go from beginning to end (Ctrl-End): 15 to 22 sec.
- Go from end to beginning (Ctrl-Home): 14 to 17 sec.
- Save file after modification: 22 sec.

When search (forward) was performed after save, it took 21 sec.

Then I opened the file in read-only mode (with Fast Browse Mode enabled).
Here are the times:

- Search forward: 4 sec
- Search reverse: 44 sec
- Ctrl-End: 0 sec
- Ctrl-Home: 0 sec

Copying the file using DOS copy command took 12 sec.


> See this page for details:
> http://www.vedit.com/huge_files.htm

BTW, On that page it says that multiple replaces can be done with Wildfile Wizard.
I don't think that is correct. However, there is macro huge-sr.vdm which does that.

--
Pauli

 


Topic: Re: VEDIT Performance (4 of 5), Read 26 times
Conf: Installation, Configuration
From: Ted Green
Date: Thursday, September 13, 2007 05:42 PM

At 09:04 AM 9/13/2007, you wrote:
>From: "Pauli Lindgren"
>
>On 9/12/2007 11:44:37 AM, Ted Green wrote:
>>
>> We do suggest that when you reach the end of a huge
>> (20Meg+) file, that instead of going to the beginning, that
>> you close the file and re-open it. You can create a hot-key
>> to do this; the close re-open time is nearly instantaneous.
>
>That only helps if you have not edited the file.
>If the file has been changed, it will be saved, which takes more time than Ctrl-Home.

That is actually not correct. Even if the file has been edited and you are at the end of a huge file, it will close in a fraction of a second and you can instantly re-open it at the beginning too.

>If the file is not to be edited, it is better to open it as Read Only.
>This makes searches and moving around file much faster.

That is absolutely correct! Navigating within the file is nearly instantaneous.

Ted.

 


Topic: Re: VEDIT Performance (5 of 5), Read 26 times
Conf: Installation, Configuration
From: Pauli Lindgren
Date: Friday, September 14, 2007 07:32 AM

On 9/13/2007 5:42:52 PM, Ted Green wrote:
>
>That is actually not correct. Even if
>the file has been edited and you are at
>the end of a huge file, it will close in
>a fraction of a second and you can
>instantly re-open it at the beginning
>too.

Yes, I guess Vedit saves the changes already when you move to the end of file.

On my 440 MB test file, moving from beginning to end of file takes normally 12 seconds. When I edited the first line and then pressed Ctrl-End, it took 26 seconds to move to the end of file. Closing the file then took less than a second.

Closing the file while at the beginning of file took 22 seconds.

By the way, if I save or close a huge file after editing it, Vedit does not give any indication that it is doing something. There is no "Wait for disk" on status line, and no hourglass cursor.

(Maybe better status line text would be e.g. "Saving bigfile.txt".)

--
Pauli