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: 26
Posts: 26   Pages: 3   [ Previous Page | 1 2 3 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 10049 times and has 25 replies Next Thread
Dark Angel
Veteran Cruncher
Australia
Joined: Nov 11, 2005
Post Count: 728
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Faster crunching

By the same token, if we don't support SOME older systems then we lose TON of possible contributions and risk p$$$ing off people who have more to offer than a single cutting edge machine. Most of the grid, I would suggest, is made up of machines over 2 years old. My particular situation allows me to run a limited number of older machines but prevents me from buying new hardware.
But we do have to draw a line somewhere, or code the science apps so that they recognise and use the best available instructions on whatever architecture they're on, which I strongly expect to be a substantial undertaking to say the least and could cause unpredictable work results.
I suppose the project could drop support for anything older than say 5 years without it being too suicidal ... but without pulling up a profile of what processors are currently running that could still be risky.
----------------------------------------

Currently being moderated under false pretences
[Mar 29, 2011 9:29:42 PM]   Link   Report threatening or abusive post: please login first  Go to top 
TimAndHedy
Senior Cruncher
Joined: Jan 27, 2009
Post Count: 267
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Faster crunching

I understand your wanting support for older systems, but realistically speaking, it's just not worth the time of the coders or the scientists. One i7 replaces somewhere between the equivalent of 8 and 25 systems that are older than 5 years.

In a perfect world with unlimited resources, we could have apps for everything. But then in a perfect world, we wouldn't need to run this project.


I think you may have misunderstood. Usually by default older systems are supported and there is a reluctance to cut systems off.

I expect every X64 system ever produced is currently supported by the 64 bit code.

**Edit
After some research it appears that the first X64 processor was the Opteron, April 2003. All X64 should support SSE and SSE2 instructions. So theoretically these should be used in the X64 version unless they were intentionally left out for compatibility reasons(hopefully not) along with additional registers etc.
----------------------------------------
[Edit 1 times, last edit by TimAndHedy at Mar 30, 2011 2:47:44 AM]
[Mar 30, 2011 2:05:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
TimAndHedy
Senior Cruncher
Joined: Jan 27, 2009
Post Count: 267
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Faster crunching

Note the minimum system requirements. Anything that will run XP is supported.

http://www.worldcommunitygrid.org/help/viewTopic.do?shortName=minimumreq#251

Windows XP min requirements: Pentium 233-megahertz (MHz) processor
(That would be a Pentium 2 circa 1997)

http://support.microsoft.com/kb/314865



I expect a lot of electricity is wasted due to inefficient code.
[Mar 30, 2011 2:15:27 AM]   Link   Report threatening or abusive post: please login first  Go to top 
KWSN - A Shrubbery
Master Cruncher
Joined: Jan 8, 2006
Post Count: 1585
Status: Offline
Reply to this Post  Reply with Quote 
Re: Faster crunching

In reply to both of you, yes, it supports older systems as it should. I, myself, am running a laptop with a P1 133.

But, this topic is about optimizing the compiler for Windows. That's why I suggested it simply wasn't worth the time of the coders and scientists to optimize for older machines. If we were able to double the output of a 12 year old machine, it would still require no less than 4 times the power of something four years old and do far less work.

This is the trade-off to which I was referring.
----------------------------------------

Distributed computing volunteer since September 27, 2000
[Mar 30, 2011 2:25:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sgt.Joe
Ace Cruncher
USA
Joined: Jul 4, 2006
Post Count: 7846
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Faster crunching

As an example, I have a Pentium Pro 200MHz machine running Windows 2000 here that returned a HCC unit in the last six months (just for a laugh. It took close to a week to finish it.)


Thanks. You have satisfied my curiosity. HCC is, I believe, the least demanding project currently being run. I was debating trying to run HCC on a an old P5 just to see how it would do, but if it took a week on Pentium Pro it would probably take 8-9 days on the P5. I think that would be the minimum system you could use as I think the 486 maxed out at 64 Meg of memory, so it would probably not meet the memory requirements for the system even though the processor would do the job, chugging along for a fortnight at least. laughing

Cheers
----------------------------------------
Sgt. Joe
*Minnesota Crunchers*
[Mar 30, 2011 2:36:05 AM]   Link   Report threatening or abusive post: please login first  Go to top 
sk..
Master Cruncher
http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif
Joined: Mar 22, 2007
Post Count: 2324
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Faster crunching

On the most efficient project - The power requirements for different projects is different; for example if your system ran 4 HPF2 tasks it might use 160W at the wall, but only 140W when crunching HCC, and 150W for HFCC (not actual values, just an example). The more refined the code, the more the CPU is used, the faster the tasks, but the more power is required.

This is something worth noting for a couple of reasons:
If you overclock, you need to watch what your power usage is in case it starts to stress the system too much when you change projects (BSOD, Restarts, hangs, task failures).
If you reduce your input during the hotter summer months, one option might be to change what you crunch for (lower wattage tasks) and perhaps reduce your clocks a bit.
[Mar 30, 2011 3:29:37 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 26   Pages: 3   [ Previous Page | 1 2 3 ]
[ Jump to Last Post ]
Post new Thread