CPU utilization never goes above 50% in Fortran code

From: Bhavesh Goswami (bhavesh0007_at_yahoo.com)
Date: 10/29/04 

Date: 29 Oct 2004 14:24:04 -0700

Hi,
  I have two separate computationally intensive FORTRAN codes, which
deals mainly in floating point operations. Whenever I run any of these
two codes on any one of the three P4 3.0GHZ, 1GB Ram machine I have in
my office, the cpu utilization is always exactly 50%, which should
actually be close to 100%. I have complied using Lahey-95 compiler
and latest Lahey Visual Studio .NET compiler, but the results are same
for both. When I run the same codes on a P4 1.3 GHZ machine, it take
100% of the CPU, so I am very confused as to why it only uses exactly
50% CPU when run on a machine with the cpu cpu speed of 3.0 GHZ. Does
anyone have any ideas on why this is happening? Any information of
ideas are greatly appreciated.

Thanks a lot,
Bhavesh Goswami

Relevant Pages

  • Re: CPU for Compaq Fortran V 6.4
    ... >Fortran V. 6.4. ... >What CPU, such as for example AMD Athlon or Intel Prescott ... Prescott or other) for a couple of codes commonly used in the nuclear ... of audio-visual rated SCSI drives, as opposed to regular SCSI drives ...
    (comp.lang.fortran)
  • Re: OT: My computers broken.
    ... the pc wouldn't boot. ... A fried CPU would result in no beep codes on some boards also. ...
    (uk.rec.motorcycles)
  • Re: Power-on Sef-Test Code
    ... Can someone explain what "B" means or where I can fin the description of the self-test codes. ... This is details in the KAnnn CPU maintenance guide, never appeared in the VAX operational or other documentation sadly. ... The crash was most likely initiated by that fault and if they still have the log of the crash from the console that may help in the detailed diagnosis. ...
    (comp.os.vms)
  • Re: C to assembly compiler - How do I handle this situation?
    ... >> RS decoding software into assembly codes. ... > You're clever enough to design your own CPU, ... designing a 32-bit CPU that uses ARM instrctions is only a matter of time ...
    (comp.arch.embedded)