Welcome to MilkyWay@home

Posts by MichaelMac

1) Message boards : Number crunching : Not Getting WUs Suddenly (Message 55637)
Posted 2 Oct 2012 by MichaelMac
Post:
Well, aren't I just the plain idiot. I didn't have CPU enabled on my preferences. This is the only rig I have without a GPU to use. I switched preferences, and it's working once more. I must have messed with the preferences at some time in the past and forgot about it.

Thanks for everyone's help!
2) Message boards : Number crunching : Not Getting WUs Suddenly (Message 55636)
Posted 2 Oct 2012 by MichaelMac
Post:
10/2/2012 9:29:23 AM | | [work_fetch] work fetch start
10/2/2012 9:29:23 AM | | [work_fetch] ------- start work fetch state -------
10/2/2012 9:29:23 AM | | [work_fetch] target work buffer: 43200.00 + 86400.00 sec
10/2/2012 9:29:23 AM | Milkyway@Home | [work_fetch] REC 229.802 priority -1.000000
10/2/2012 9:29:23 AM | | [work_fetch] CPU: shortfall 129600.00 nidle 1.00 saturated 0.00 busy 0.00
10/2/2012 9:29:23 AM | Milkyway@Home | [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) (blocked by prefs)
10/2/2012 9:29:23 AM | | [work_fetch] ------- end work fetch state -------
10/2/2012 9:29:23 AM | | [work_fetch] No project chosen for work fetch


Ok, this what I got when I turned on work_fetch_debug. Can anyone tell me what the problem is?

Thanks!

-Michael
3) Message boards : Number crunching : Not Getting WUs Suddenly (Message 55612)
Posted 26 Sep 2012 by MichaelMac
Post:
I wish the event log would be more specific as to the reasons it's not fetching wus.

work_fetch_debug, see Client_configuration.


Ahhh, I'll give that a go! Thanks!
4) Message boards : Number crunching : Not Getting WUs Suddenly (Message 55610)
Posted 26 Sep 2012 by MichaelMac
Post:

Could it be your other projects have filled up your cache and Boinc doesn't think you could finish some MW work in time if you got it? IF this is true then Boinc will cycle thru all the projects eventually and you just need to wait it out.


One of them is running another project (Einstein) but the other is just running Milkyway. I'll wait it out on the one running the other project to see if the cache is the problem. Not sure about the other one.

It's not a big deal, they don't crunch a lot, but they do contribute. I wish the event log would be more specific as to the reasons it's not fetching wus.
5) Message boards : Number crunching : Not Getting WUs Suddenly (Message 55605)
Posted 25 Sep 2012 by MichaelMac
Post:
I have two of my machines that suddenly stopped getting WU. I can't tell why. The event log isn't forthcoming with the reasoning. My other machines appear to be fine.

I'm running BOINC 7.0.28, and these two particular machines are W2K Server. I'm only running CPU WUs no GPUs.

The IDs of the two machines are: 466255 and 438755

9/25/2012 9:28:13 AM | Milkyway@Home | Sending scheduler request: To report completed tasks.
9/25/2012 9:28:13 AM | Milkyway@Home | Reporting 4 completed tasks, not requesting new tasks
9/25/2012 9:28:15 AM | Milkyway@Home | Scheduler request completed


I've tried requesting an update, and I've tried resetting the project.

Any ideas?

Thanks!

-MichaelMac
6) Message boards : Number crunching : GPU and CPU Crunch on Both (Message 54331)
Posted 5 May 2012 by MichaelMac
Post:
Quad Core PC
7) Message boards : Number crunching : GPU and CPU Crunch on Both (Message 54317)
Posted 4 May 2012 by MichaelMac
Post:

It is probably the setting to crunch while the pc is 'in use', this is in the Boinc Manager, down by the clock, and then under the Tools, computing preferences, processor usage links. Be sure to click ok at the bottom to save any changes or they will be lost.


I should have mentioned this before, but I do have that set to crunch while "in use".

So, I set this particular computer to a different venue so I could change its settings without affecting the other computers running Milkyway. I turned off CPU and am just running GPU tasks. That's what it is doing now, so it's happily crunching away for both Test4Theory and Milkyway BUT the CPU is under utilitized. I won't complain, but I'd still like to figure out how to get that CPU running some of the Milkyway stuff.

Thanks for your response!
8) Message boards : Number crunching : GPU and CPU Crunch on Both (Message 54308)
Posted 3 May 2012 by MichaelMac
Post:
I'm fairly new at this, and although I'm beginning to understand a lot of what's going on, I still feel a bit in the dark.

I'm running Boinc 7.0.25 on a Quad Core system with NVidia GPU. I have both GPU and CPU tasks queued, but only the GPU task is running. The CPU task says "waiting to run".

I have the % of processors set to 75% so one cpu core would be available to vbox for LHC Test4Theory to run. That leaves 3 CPUs (which is what the Event Log shows).

The Test4Theory runs, the Milkyway GPU task runs, but the Milkyway CPU task is "waiting to run".

Now, for grins, I switched the % of processors to 100%. The Test4Theory went to "waiting to run" state, the vbox shut down, and THEN the Milkyway GPU and CPU were both running.

Any ideas why that is? And, more importantly, how I can get both the Milkyway GPU and CPU tasks running? I must be missing something.

Thanks!




©2024 Astroinformatics Group