Re: gfortran, g95, and dual-core
- From: "Dr Ivan D. Reid" <Ivan.Reid@xxxxxxxxxxxx>
- Date: Sun, 30 Sep 2007 11:51:35 +0000 (UTC)
On Sat, 29 Sep 2007 14:38:17 -0600, Charles Russell <NOSPAM@xxxxxxxxxxxxx>
wrote in <xtyLi.83797$Lu.51133@xxxxxxxxxxxxxxxxxxxxxx>:
So computing time is not simply a matter of counting "flops" (defined in
Golub & Van Loan "Matrix Computations" (1983) as the cost of "a floating
point add, a floating point multiply, and a little subscripting")
because of the complicating factor of cache. The simple model was so
much nicer.
For an analysis of a fairly complex piece of software (in C++
rather than Fortran, but that's largely irrelevant) look at the paper
and/or slides here:
http://indico.cern.ch/contributionDisplay.py?contribId=259&sessionId=28&confId=3580
http://indico.cern.ch/contributionDisplay.py?contribId=490&sessionId=13&confId=3580
For several reasons we're nowhere near to using the full capabilities
of our CPUs.
--
Ivan Reid, School of Engineering & Design, _____________ CMS Collaboration,
Brunel University. Ivan.Reid@[brunel.ac.uk|cern.ch] Room 40-1-B12, CERN
KotPT -- "for stupidity above and beyond the call of duty".
.
- References:
- gfortran, g95, and dual-core
- From: Charles Russell
- Re: gfortran, g95, and dual-core
- From: Richard Maine
- Re: gfortran, g95, and dual-core
- From: Charles Russell
- gfortran, g95, and dual-core
- Prev by Date: Re: Windows array allocation problem
- Next by Date: Re: Variable Precision Problem
- Previous by thread: Re: gfortran, g95, and dual-core
- Next by thread: Re: gfortran, g95, and dual-core
- Index(es):