Message boards : Number crunching : Optimised for AMD?
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile adrianxw

Send message
Joined: 29 Sep 04
Posts: 187
Credit: 705,487
RAC: 0
Message 8028 - Posted: 9 Jun 2005, 9:01:00 UTC
Last modified: 9 Jun 2005, 9:03:29 UTC

I looked at the results for the recent wu's I had. In all cases, machines equipped with AMD processors returned the units in substantially shorter times, often as much as 50% of the time.

This result for example. The Intel chipped machines both returned figures 15-16,000 seconds, the two AMD machines, ~7,000.

Another. Different figures but same trend.

Any comments anyone?

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
ID: 8028 · Report as offensive     Reply Quote
Profile The Gas Giant

Send message
Joined: 2 Sep 04
Posts: 309
Credit: 715,258
RAC: 0
Message 8029 - Posted: 9 Jun 2005, 9:45:01 UTC

One machine (yours) is an HT machine so in reality divide your cpu time by 2 to get an 'equivalent' AMD time. The other INTEL machine is a 2.4GHz chip so is slow in any case. The variation in claimed credit is fairly typical.

Live long and crunch!

Paul
(S@H1 8888)
BOINC/SAH BETA
ID: 8029 · Report as offensive     Reply Quote
Profile sysfried

Send message
Joined: 27 Sep 04
Posts: 282
Credit: 1,415,417
RAC: 0
Message 8030 - Posted: 9 Jun 2005, 11:05:56 UTC - in response to Message 8029.  

> One machine (yours) is an HT machine so in reality divide your cpu time by 2
> to get an 'equivalent' AMD time. The other INTEL machine is a 2.4GHz chip so
> is slow in any case. The variation in claimed credit is fairly typical.
>
> Live long and crunch!
>
>
Yeah, that's a HT issue... :-)
ID: 8030 · Report as offensive     Reply Quote
Profile adrianxw

Send message
Joined: 29 Sep 04
Posts: 187
Credit: 705,487
RAC: 0
Message 8031 - Posted: 9 Jun 2005, 11:22:57 UTC
Last modified: 9 Jun 2005, 11:24:08 UTC

Ignore my machine, in the first example I gave, 35696 is a 2600 Athlon and 22101 a 2400 Intel yet the Athlon cranked the wu in 7,755 seconds and the Intel, (non HT), took 15,953. That is a very big difference, less then half the time. Why is that?

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
ID: 8031 · Report as offensive     Reply Quote
Travis DJ

Send message
Joined: 29 Sep 04
Posts: 196
Credit: 207,040
RAC: 0
Message 8032 - Posted: 9 Jun 2005, 13:38:29 UTC - in response to Message 8031.  

> That is a very big difference, less then half the time. Why is that?

Per clock cycle, AthlonXP & Athlon64 machines perform more work. The answer is far more complicated than that but the easist to go with. :)

ID: 8032 · Report as offensive     Reply Quote
Gaspode the UnDressed

Send message
Joined: 1 Sep 04
Posts: 506
Credit: 118,619
RAC: 0
Message 8033 - Posted: 9 Jun 2005, 13:41:45 UTC

Some of these differences are due to the differing development paths taken by Intel and AMD with their successive generations of processors. Intel have optimised their P4 around multimedia applications, games, et al, at the expense of the FPU. A P3 FPU would be faster than a P$ unit at the same clock frequency. AMD have concentrated their efforts in other ways, so their FPU is significantly faster than Intel's. On a like for like basis the AMD chip will outperform an Intel chip on floating point operations.


Gaspode the UnDressed
http://www.littlevale.co.uk
ID: 8033 · Report as offensive     Reply Quote
Profile adrianxw

Send message
Joined: 29 Sep 04
Posts: 187
Credit: 705,487
RAC: 0
Message 8034 - Posted: 9 Jun 2005, 15:03:57 UTC

Must be project dependent as this S@H result has the longest crunch times for the AMD's and the Intels performing best.

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
ID: 8034 · Report as offensive     Reply Quote
Profile Keck_Komputers

Send message
Joined: 1 Sep 04
Posts: 275
Credit: 2,652,452
RAC: 0
Message 8041 - Posted: 10 Jun 2005, 3:15:22 UTC - in response to Message 8034.  

> Must be project dependent as <a> href="http://setiweb.ssl.berkeley.edu/workunit.php?wuid=17143831">this S@H
> result[/url] has the longest crunch times for the AMD's and the Intels
> performing best.
>
The P4s make up for the lack in the FPU with a larger cache. The seti app is small enough to fit into the cache most of the time so the P4s can do them quicker since there are fewer calls to main memory. The complier used and the options used when compiling can also make a difference.
BOINC WIKI

BOINCing since 2002/12/8
ID: 8041 · Report as offensive     Reply Quote

Message boards : Number crunching : Optimised for AMD?


©2024 CERN