Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 5
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1635 times and has 4 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Testing the same FAH WU on different machines?

Hi there.
My Motherboard Blew on my old computer, which was a p4 quad core 2.4ghz.
I now have a new motherboard with an AMD Phenom(tm) II X4 955
Processor
3.21 GHz. This is a borrowed machine until my It friend has some free time so he can bring me my new machine and set it up.
Has anyone ever tried testing the same FAH work unit on different machines to see how long it takes each one to complete?
Also, If a work unit takes 11 hours to complete on a 32 bit system, and you then tried running it under windows 7 64 bit, would there be any speed difference?
Cheers and thanks.
[Apr 19, 2014 8:34:55 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Testing the same FAH WU on different machines?

It's said that running the same under 64bit os gains about 4-8 percent in speed. It can also happen that it runs slower in 64 bit, jaw down. Boinc is supposed to test this over a series of some 20+ tasks but cannot find if wcg has activated this feature, running a set with the 32 bit app, then a comparable set with 64 bit app. There were some user reports of the 64 bit being slower from the stable runtime hcc1 project. Presently with the highly variable runtimes we see it's hard to compare.

Requested in past, a reference workunit set, so we can ad nauseum test them on various platforms and configurations. A separate feed would be needed, one that will not go into my contributions wink . Of course, this will only serve a fraction of the volunteers. Most all only want the easiest form of idle time computing, else they zone out and disconnect. The auto-testing would take care of optimization, and with the fast database wcg has of the devices, cpus, osses etc, it really should be set and forget autonomously best performance assigning.
[Apr 19, 2014 1:33:09 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sgt.Joe
Ace Cruncher
USA
Joined: Jul 4, 2006
Post Count: 7844
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Testing the same FAH WU on different machines?

p4 quad core 2.4ghz

??????????????????
I was unaware they ever made such a thing. I think the fastest P4 was 3.4gz with HT. You might mean a Q6600 at 2.4gz which is definitely not a P4.
Cheers
----------------------------------------
Sgt. Joe
*Minnesota Crunchers*
[Apr 19, 2014 2:47:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Testing the same FAH WU on different machines?

Whoops, Yes, you're right.
[Apr 19, 2014 10:47:28 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Testing the same FAH WU on different machines?

There is a way you can test the same work unit on different machine.
You simply install boinc on each machine, and then copy the boinc data directory.
[Apr 19, 2014 10:53:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread