Re: Command line programs and windows XP
From: Michael Prager (Mike.Prager.indigo_at_noaa.gov)
Date: 05/11/04
- Next message: Dr Chaos: "Re: Is FORTRAN a dying language?"
- Previous message: glen herrmannsfeldt: "Re: Illegal instruction (core dumped)"
- In reply to: Stephen White: "Command line programs and windows XP"
- Next in thread: Tim Prince: "Re: Command line programs and windows XP"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 11 May 2004 13:45:09 -0400
"Stephen White" <S.White@irl.cri.nz> wrote:
>I have a moderately complex fortran program, compiled with Compaq visual
>fortran. This is run from the command line.
> If I run this with output to the screen it runs in a few seconds and gets
>almost 100% of the CPU.
> If output is to a file (opened in the program) then it takes minutes to run
>getting between 0 - 5 % of the CPU.
>Running with output to stdout but redirected to a file (>) is also slow but
>faster than when the file is opened in the program (different buffer sizes
>?)
>
>I have tried playing around with system settings for foreground and
>background without changing this behaviour.
>
>has anyony any suggestions as to whatt is causing this and how to fix it?
>
>Steve
>
>
Have you tried changing (increasing) the block size for the
external file?
>
-- Mike Prager, NOAA, Beaufort, NC Address spam-trapped; remove color to reply. * Opinions expressed are personal and not represented otherwise. * Any use of tradenames does not constitute a NOAA endorsement.
- Next message: Dr Chaos: "Re: Is FORTRAN a dying language?"
- Previous message: glen herrmannsfeldt: "Re: Illegal instruction (core dumped)"
- In reply to: Stephen White: "Command line programs and windows XP"
- Next in thread: Tim Prince: "Re: Command line programs and windows XP"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|