Rick,

Donate@Home was a success for us because we had access to a lot of (AMD) GPU that we weren't using for anything else, at a time before ASICs when it was still possible mine Bitcoins usiing normal hardware.

We saw the effect of the introduction of ASICs almost immediately (indeed long before most of the customers actually received theirs, why that was is left as an exercise for the reader) and our return dropped to almost nothing very quickly.

Shortly after that happened we stopped the project as the human effort to run it couldn't be justified in the absence of any return. We're still accepting Bitcoin donations via direct transfer however.

I understand that some of you have ASICs now but, frankly, I doubt there'll be enough to make a worthwhile mining pool. Happy to be proven wrong, but I'd need to make a straw poll of crunchers to see.

Right now, however, if you do have ASIC mining hardware and want to generate Bitcoins for GPUGRID, firstly: thank you! and secondly: the best I can suggest is you subscribe to one of the large mining pools and reap a share of their activity, then xfer that to us.

Cheers,

Matt

MJH,
Why not resurrect Donate@home, and allow us to use our ASIC miners to find cash for gpugrid like we use to with our GPU's? Right now all my miners are crunching for milkyway@home via Bitcoin Utopia, but I'd love to switch some over to you. BTW Bitcoin Utopia has wu's for: ASIC miners only, cpu only, AND GPU only. if they think it's worthwhile, maybe you should reconsider. Just a thought.
Regards,
Col. Rick A. Sponholz

I figured out a reason for overfetch in my BOINC 7.1.18:

I have GPU-Grid set up as backup project, with POEM being primary and providing sporadic work supply. The cache setting is relatively low (0.05 + 0.35 days) and long runs take ~11 hours (0.46 days) on my GPU.

Yet, when POEM ran out BOINC got 2 GPU-Grids. I increased the time to switch between apps to 15h to make it finish the 1st WU which already started, but the other one may sit there for days without starting when POEM supplied work again.

So there I sat thinking why the **** does BOINC fetch 22h worth of work when it's supposed to get at most 1 for a backup project anyway? Why not wait until the 1st WU is almost finished, or at least when the expected remaining runtime falls below the cache setting? This made me switch to short tasks, where the entire problem is just not as large.

Today I think I figured out what's happening: I switched to long-runs again and got a beta WU, where this didn't happen (only fetched one, as it should). The difference on my side between beta and long run? The former is set to 1 GPU, whereas the latter is set to 0.51 to allow up to 3 POEMs along the GPU-Grid task, increasing GPU utilization from ~85% to 98%.

Apparently BOINC sees a nVidia not fully utilized when the backup project kicks in (correct, it's only 0.51), but does not yet factor in that fetching another WU of 0.51 won't help in this case. On the other hand this behaviour is not too bad, since with correct backup-project-behaviour I'd have to wait for the download of the new WU when the current one finishes. And I'd rather miss some early-return bonus than risk an idle GPU ;)

Long story short: do you have less than 1 GPU set per GPU-Grid task?

MrS

I believe you need a load on the intel VGA (or DVI) port. One way is to plug a monitor in. Another way would be to use a dummy vga plug. The way most bios's are set up is if they don't detect a device on the iGPU and you have another graphics card they simply disable the iGPU

Also if you get the intel GPU driver through windows update its not usable for crunching. You need to get the 'full' package from the intel download centre.

Probably a bit late but maybe it will help someone else.

Unfortunately, I guess you can't run the Intel HD processor if you already have two dual processor video cards in your box. It cost me $60 and an 80 mile trip to the computer store to find that out. But thanks for trying to help. Regards, Rick

Don't see why that would be the situation. Did they mention why, or just charge you $60 and say it can't be done?
Have you tried to use the IHD4600 to support your primary monitor?
While I don't have two dual GPU's in any system, I do have 3 discrete GPU's in one system and I can use my iHD4000 GPU to run Einstein.

Unfortunately, I guess you can't run the Intel HD processor if you already have two dual processor video cards in your box. It cost me $60 and an 80 mile trip to the computer store to find that out. But thanks for trying to help. Regards, Rick

Don't see why that would be the situation. Did they mention why?
Have you tried to use the IHD4600 to support your primary monitor?
While I don't have two dual GPU's in any system, I do have 3 discrete GPU's in one system and I can use my iHD4000 GPU to run Einstein.

Rick, see the following thread in Einstein,
http://einstein.phys.uwm.edu/forum_thread.php?id=10215&nowrap=true#125627

Just after deleting my exclude intel_gpu, and immediately got,
GPUGRID - Requesting new tasks for intel_gpu

- Obviously I wouldn’t get Intel work, but I thought it might change the scheduler causing it to cache up more work, some wonky way. Unfortunately I can't test for this because the 2 WU's I have running are 3h and 6h into a run and Boinc thinks they will take another 60h and 70h (due to the estimates).

Rick, you can download the Intel drivers and use it at Einstein.

Help!

I've been at this all day. After booting I get many "Display driver stopped responding and has recovered". After six or seven of these I get a blue screen with stop code X00000116. Googling tells me it may be my GTX 660. I replaced it with my GTX 460. Still the same.

If I turn off BOINC al,l is sweetness and light!

What to do??

The estimated remaining runtime could well be incorrect (due to the recent short and long test work units all being described as 5M Gflops server side).

Any Network Usage restrictions in place?

I cant see your app_config or settings.
So, is your i7-4770's Intel HD4600 GPU being seen by Boinc (it would say in the first page of your Boinc Log file)?

If so then you can exclude the intel_GPU from being 'used' by GPUGrid (you maybe already did this).

If the intel_GPU is being seen by Boinc and you have not excluded it from the GPUGrid project, your buffer settings will mean you cache up to 4h of work, for 5 GPU's.

This might help you work out what's going on,
http://www.gpugrid.net/host_app_versions.php?hostid=157727

You can see what your different app performances are listed as for that system.
Should be going by 'Average turnaround time 0.66 days'

That was what I thought, but when I put "acemd.800-55.exe" or "acemd.800-55" or "acemd_800_55" and about 10 other variations, BOINC did not recognize the app name. Couriously, the new long app seems to accept the variables of the old "acemdlong" app name in my app_config.xml file. Rick

I get the app names from looking in the client_state.xml file, within the <app> blocks.