Compiled AMD64 client takes 8 hours


Advanced search

Questions and Answers : Unix/Linux : Compiled AMD64 client takes 8 hours
Message board moderation

To post messages, you must log in.

AuthorMessage
Hugh Waite

Send message
Joined: 17 May 99
Posts: 3
Credit: 96,052
RAC: 0
United Kingdom
Message 95682 - Posted: 6 Apr 2005, 18:45:32 UTC
Last modified: 6 Apr 2005, 18:47:23 UTC

As an AMD64 user I have downloaded the source for BOINC & SETI and compiled them both.
BOINC was optimised with
-march=x86-64 -O3 -falign-functions=4 -fprefetch-loop-arrays -fomit-frame-pointer -fforce-addr -ftracer
and SETI was compiled with the same flags
I have an AMD64 3400+ and the BOINC benchmarks are
2039 MFLOPS
4378 MIPS
but SETI takes ~7-8 hours to do one unit compared to other people doing the same unit ~2-3 hours.
I am using
boinc_public-cvs-2005-04-03 and
seti_boinc-client-cvs-2005-04-03
Does anyone have any ideas about this?
Thanks, Hugh
ID: 95682 · Report as offensive
Profile spacemeat
Avatar

Send message
Joined: 4 Oct 99
Posts: 239
Credit: 8,425,288
RAC: 0
United States
Message 95729 - Posted: 6 Apr 2005, 21:48:32 UTC

same here. my flags were "-march=athlon64 -O2 -pipe -ffast-math -fomit-frame-pointer -falign-functions=4"
older source had the same problems, wu's were taking over 10 hours each.

the same pc gets 2 hr WU's using a client i compiled on a p2-300 using the same flags, except with -mcpu=i686. both machines used gcc-3.4.3
ID: 95729 · Report as offensive

Questions and Answers : Unix/Linux : Compiled AMD64 client takes 8 hours


 
©2025 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.