Welcome to MilkyWay@home

Looking to optimize number crunching

Message boards : Number crunching : Looking to optimize number crunching
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Firewagon

Send message
Joined: 1 Sep 11
Posts: 3
Credit: 4,400,077
RAC: 0
Message 58057 - Posted: 30 Apr 2013, 2:54:25 UTC

Hope this is the right place.
The reason for this thread is I just notice a new Work Unit (N-Body Simulation 1.08 "349110070) with 1200+ hours until completion. This is gonna blow the deadline of 05/11/2013 unless the estimate is way off. Most other estimate are bang on though at + or - a few minutes.

I have 2 questions:
1 - How can I optimize the number crunching? The only custom I did was give boinc permission to run for all users (me only as Admin or MeTheUser) since I don't use the Admin account for day to day stuff. Since the Install I let boinc do it's thing but don't interfere. Boinc is set to suspend when I play my games (see below).
2 - Screen tearing. Every once in a while I get bad(blank - no color) pixels in my display. This only seems to happen when boinc is running. I am hoping that any custom I set here will also fix this, but probably not. It is probably a driver issue.

My Computer Specs:
CPU: AMD FX8320 - 8 core Black Edition
RAM: 12 GIG (soon to be 8 gig instead, donating 4 gig to 2nd computer with bad ram)
OS: Windows 7 Home Premium, Service pack 1
Video Card: Sapphire HD7770 PCIE
Video Driver: Catalyst 13.1
BOINC Ver: 7.0.28 (X64)

Please note this is primarily a gaming system. I play World of Warcraft, FarCry3, and soon Crysis3.

Any ideas?

“Any fool can know. The point is to understand.”
― Albert Einstein

I on the other hand am just confused.
ID: 58057 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Firewagon

Send message
Joined: 1 Sep 11
Posts: 3
Credit: 4,400,077
RAC: 0
Message 58070 - Posted: 30 Apr 2013, 22:42:06 UTC

OK... seriously confused.....

When I went to bed last night, the computer had 5 N-body WU running with at least 800 hours estimated to completion each. Now they are all complete and either validated, or awaiting validation.

Is the estimated time to completion that far out of whack?
Just before bed I had told boinc to not get new tasks so it could concentrate on finishing what it had.

This gives new meaning to estimate.... 800 hours completed in less than 24.

Is this normal?
“Any fool can know. The point is to understand.”
― Albert Einstein

I on the other hand am just confused.
ID: 58070 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 8 May 09
Posts: 3334
Credit: 524,010,781
RAC: 2,126
Message 58074 - Posted: 1 May 2013, 11:07:20 UTC - in response to Message 58070.  

OK... seriously confused.....

When I went to bed last night, the computer had 5 N-body WU running with at least 800 hours estimated to completion each. Now they are all complete and either validated, or awaiting validation.

Is the estimated time to completion that far out of whack?
Just before bed I had told boinc to not get new tasks so it could concentrate on finishing what it had.

This gives new meaning to estimate.... 800 hours completed in less than 24.

Is this normal?


As you finish units the time to completion gets recalculated for each of the remaining and any new units that you get. As you then finish those units in a more 'normal' time frame the time to completion will come down and you will get more units again. What you are seeing IS normal behavior for a pc that has had a so called 'stuck' unit and is now moving forwards. Some units are much more complicated then even the project folks can guess, so it can take a very long time sometimes. This does NOT mean you found something, it just means the unit had lots of stuff in it that it had to go thru that normal units don't. In the case of a gpu unit it happens when the the gpu crashes and the cpu takes over crunching the unit. But the n-body units are cpu units not gpu units. Over the next several days Boinc will bring the time to completion back down to the more normal for you time frame again. I had a project go from 45 minutes to 7 hours, it took almost a week to come back to normal again.
ID: 58074 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Looking to optimize number crunching

©2024 Astroinformatics Group