CMD in WinXP

I just loaded WinXP on my wife's computer. I hate that OS.

I just noticed that the command prompt window scrolls
real slow. I did some searching and don't see an easy way
to correct this. Does anybody have a recommendation
on how to fix it?

Obviously, I could just output my Perl output to a test file,
but I'd like an way to fix the cmd window so I wouldn't
need a separate list of perl scripts to run on the WinXP
computer.


Mike Flannigan

Re: CMD in WinXP

> ...command prompt window scrolls real slow....

Are you saying that perl scripts process slowly? Either you have other
processes running that are gobbling up resources and slowing you down
and/or your script maybe needs to be reworked to make it faster.

Re: CMD in WinXP

goldtech wrote:

>> ...command prompt window scrolls real slow....
>
>Are you saying that perl scripts process slowly? Either you have other
>processes running that are gobbling up resources and slowing you down
>and/or your script maybe needs to be reworked to make it faster.

Well, no. I agree with the OP, print()ing to the terminal in Windows is
quite slow. I am not sure if it's the actual scrolling of the text or if
printing even small text pieces involves a large overhead and thus slows
down the process. Either way it can be somewhat annoying.

I believe one workaround may be to do your own buffering and print()ing the
data in larger chunks instead of in many small pieces.

jue

Re: CMD in WinXP

Post removed (X-No-Archive: yes)

Re: CMD in WinXP

still just me wrote:

> On Sun, 23 Dec 2007 19:58:01 GMT, Jürgen Exner
> wrote:
>
> >Well, no. I agree with the OP, print()ing to the terminal in Windows is
> >quite slow.
>
> I have to go with the first followup - I don't have a particularly
> fast computer and yet printing output or error output is
> instantaneous.
>
> I think it's a system issue for the OP. What about other output to the
> command window from other MS Windows commands? How fast is a "dir" in
> a large directory?

Actually, Jurgen is correct.

Perl scripts run real fast as long as there is no output to
the cmd window. Even with output, if you have a
clear screen the output is real fast to fill up the window,
but then slows way down to print line-by-line, I guess
so you can read the output.

This only happens on XP. Win2000 cmd window is
super fast. I guess this is another "feature" MS made
to screw things up. I sure wish I could get the Win2000
cmd window over to XP, but just copying it over
produces the same effect.

I don't see any easy fixes, so I guess outputting to a file
and then opening the file is the way to go. Very annoying.


Thanks for the responses.


Mike

Re: CMD in WinXP

Mike Flannigan wrote:
>
> still just me wrote:
>
>> On Sun, 23 Dec 2007 19:58:01 GMT, Jürgen Exner
>> wrote:
>>
>>> Well, no. I agree with the OP, print()ing to the terminal in Windows is
>>> quite slow.
>> I have to go with the first followup - I don't have a particularly
>> fast computer and yet printing output or error output is
>> instantaneous.
>>
>> I think it's a system issue for the OP. What about other output to the
>> command window from other MS Windows commands? How fast is a "dir" in
>> a large directory?
>
> Actually, Jurgen is correct.
>
> Perl scripts run real fast as long as there is no output to
> the cmd window. Even with output, if you have a
> clear screen the output is real fast to fill up the window,
> but then slows way down to print line-by-line, I guess
> so you can read the output.
>
> This only happens on XP. Win2000 cmd window is
> super fast. I guess this is another "feature" MS made
> to screw things up. I sure wish I could get the Win2000
> cmd window over to XP, but just copying it over
> produces the same effect.
>
> I don't see any easy fixes, so I guess outputting to a file
> and then opening the file is the way to go. Very annoying.
>
>
> Thanks for the responses.
>
>
> Mike
>
>

Does increasing the Command Prompts "Screen Buffer Size" improve
performance?

Command prompts on my XP laptop and Win2000 Server perform similarly.

For example, perl -e "for my $i (0 .. 10000) { print qq($i\n)}"
takes 02.553 seconds on my 3GHz server and 02.723 seconds on my 2GHz laptop.
--

Len

Re: CMD in WinXP

Mike Flannigan writes:

> Perl scripts run real fast as long as there is no output to
> the cmd window. Even with output, if you have a
> clear screen the output is real fast to fill up the window,
> but then slows way down to print line-by-line, I guess
> so you can read the output.
>
> This only happens on XP. Win2000 cmd window is
> super fast. I guess this is another "feature" MS made
> to screw things up. I sure wish I could get the Win2000
> cmd window over to XP, but just copying it over
> produces the same effect.

Try console-2.00 from

http://sourceforge.net/project/showfiles.php?group_id=43764& package_id=36333&release_id=414524

which appears much faster than windows cmd.

--
Radek

Re: CMD in WinXP

Mike Flannigan wrote:

> Actually, Jurgen is correct.
>
> Perl scripts run real fast as long as there is no output to
> the cmd window. Even with output, if you have a
> clear screen the output is real fast to fill up the window,
> but then slows way down to print line-by-line, I guess
> so you can read the output.
>
> This only happens on XP. Win2000 cmd window is
> super fast. I guess this is another "feature" MS made
> to screw things up. I sure wish I could get the Win2000
> cmd window over to XP, but just copying it over
> produces the same effect.
>
> I don't see any easy fixes, so I guess outputting to a file
> and then opening the file is the way to go. Very annoying.
>
> Thanks for the responses.
>
> Mike

Thanks for all the comments. Very good comments.
I plan to check into the console-2.00.

My searches of this problem led me to believe that it
was endemic to the WinXP OS. One informed
gentleman told me it is an indication that the graphics
drivers are not set up correctly. When I went back to
correct the problem, I was surprised to see the CMD
window now scrolls very fast - same as my Win2000
computer. It must be something I did, since I had MS
Update turned off, but I'm not sure what I did right.

My elapsed time on
for my $i (0 .. 10000) { print qq($i\n)}
is between 0.25 and 0.266 seconds on the Win2000
computer.

My elapsed time on
for my $i (0 .. 100000) { print qq($i\n)}
is 2.55 seconds on the Win2000 computer.



Mike