Hey Everyone,

Sorry I haven't been reading the forums. I have been working hard on getting the Windows GPU version running. I am going to do a rerelease as soon as I have working GPU versions. I have deprecated all of the Windows GPU applications in the meantime.

Jake

Just received 80 more Windows GPU tasks for my Radeon R9 290. Still only working on the CPU. Aborting....

Just received 80 more Windows GPU tasks for my Radeon R9 290. Still only working on the CPU. Aborting....

I didn't abort them. Crunched them all with my CPU and most of them validated OK.

Just received 80 more Windows GPU tasks for my Radeon R9 290. Still only working on the CPU. Aborting....

I didn't abort them. Crunched them all with my CPU and most of them validated OK.

Yes, they compute fine here too, but I prefer to have the GPU doing something instead of sitting idle, so it's off running SETI and Einstein just now. My CPUs can run Milkyway with proper CPU tasks anyway.

Hey Everyone,

I have been able to get a working 32 bit GPU application, but for some reason, the 64 bit has been giving me an impossible amount of trouble. For the time being I am planning to release the 32 bit application to run in both the 32 and 64 bit plan class so everyone can get crunching again and we can get some science done while I continue to work on the 64 bit application. This application will run on 64 bit platforms just fine and since we do not use a large amount of memory, there really isn't even a need for the application to be 64 bit.

Is there any objection to this plan? I'll give it an hour or so before I release to listen for opinions.

Thank you all for being great.

Jake

Hi Jake,
don't mind if its 32bit as long as it works:-)

---

Regards,
Cliff.
--
Been there Done That, still no Damn T-Shirt

Hey Everyone,

I have been able to get a working 32 bit GPU application, but for some reason, the 64 bit has been giving me an impossible amount of trouble. For the time being I am planning to release the 32 bit application to run in both the 32 and 64 bit plan class so everyone can get crunching again and we can get some science done while I continue to work on the 64 bit application. This application will run on 64 bit platforms just fine and since we do not use a large amount of memory, there really isn't even a need for the application to be 64 bit.

Is there any objection to this plan? I'll give it an hour or so before I release to listen for opinions.

Thank you all for being great.

Jake

Pull the trigger, Ladies and Gentlemen, START YOUR GPUSSSSSSS!!

Is there any objection to this plan?

I'm OK with this idea.

Is there any objection to this plan?

Thank you all for being great.

Jake

No objections .. its just going to take me a while to burn through the ones I currently have in my stash - which are sharing a core with a CPU unit

The Seti GPU-apps are all 32-bit, so i do not see any problems here, as long as there is no big memory requirements, that will run better in 64-bit environment.

In short: Pull the trigger! :)

---

Aloha, Uli

Hey Everyone,

Just released the GPU version. It is a 32-bit application that works on 64 bit machines. Let me know if there are any issues. (They should take about 5x longer than normal work units since you are crunching 5.)

Jake

Jake appreciated for your efforts.

I start new ones lets see what the results come. both amd and NVidia.

Hey Everyone,

Just released the GPU version. It is a 32-bit application that works on 64 bit machines. Let me know if there are any issues. (They should take about 5x longer than normal work units since you are crunching 5.)

Jake

Works perfectly in the expected time with 100% GPU load on Windows 10 with a Radeon R9 290.

My "GPU" is completing them ok. I assume Jake will fix this shortly so it actually computes on it and not the CPU....

For now I just leave it to it so he can see what comes back.

Your "GPU" is completing nothing. It's all on the CPU. That's what everyone is saying. No GPUs are being used with the new 1.42 WUs.

That's the reason I put "GPU" in quotes - to indicate it was a GPU task not running on the GPU. I thought I was being quite clear.

Call it what it actually is. GPU units are running on CPUs, in Windows. End of story.

Jeez, I thought it was obvious, what do you think I used the quotes for? The next sentence explained it even if you didn't understand. Nevermind....

No one can read your mind, especially on the internet. Most communication is not verbal and all that is lost on the internet. Please just say what you mean. There's enough confusion about the GPU WUs running on the CPUs.

Jake, Is the 32bit app just for Windows? Linux was was already working.

My "GPU" is completing them ok. I assume Jake will fix this shortly so it actually computes on it and not the CPU....

For now I just leave it to it so he can see what comes back.

Your "GPU" is completing nothing. It's all on the CPU. That's what everyone is saying. No GPUs are being used with the new 1.42 WUs.

That's the reason I put "GPU" in quotes - to indicate it was a GPU task not running on the GPU. I thought I was being quite clear.

Call it what it actually is. GPU units are running on CPUs, in Windows. End of story.

Jeez, I thought it was obvious, what do you think I used the quotes for? The next sentence explained it even if you didn't understand. Nevermind....

No one can read your mind, especially on the internet. Most communication is not verbal and all that is lost on the internet. Please just say what you mean. There's enough confusion about the GPU WUs running on the CPUs.

Jake, Is the 32bit app just for Windows? Linux was was already working.

Hey mmonnin,

Yes this is only for Windows. Linux GPU 64bit is actually 64bit since it was working.

Jake

No one can read your mind, especially on the internet. Most communication is not verbal and all that is lost on the internet. Please just say what you mean. There's enough confusion about the GPU WUs running on the CPUs.

I did say what I meant, in the next sentence: "so it actually computes on it and not the CPU". Although putting "GPU" in quotes should have sufficed, it's a standard technique in the English language.

AFAIK, this is currently normal, because there are 5 WUs now in 1 WU (*_bundle5_* in the WU name).
Everytime 1 WU finish of this 5 WUs, it begin again from 0%.
This happens 4 times and with calculation of the 5th WU it will finish to 100%.

Does it have to be this way? I know it's not as important as having it working, but it is a bit irritating to see the progress meter jumping all over the place.

Hey Peter,

It doesn't have to be this way. I can look at making a new release later in the week with a fix to the progress bar. Sorry about that.

Jake

First results come, they all finished "Completed, validation inconclusive" waiting "pending".

For AMD R9270x %95 GPU %5 CPU 165sec less then before 5x task
For Nvidia 750TI %85 GPU %3 CPU 566sec less then before 5xtask

I think you don't need x64 application x32 works good.

---

Hey Peter,

It doesn't have to be this way. I can look at making a new release later in the week with a fix to the progress bar. Sorry about that.

Jake

Thanks Jake, much appreciated. One quick question, is the upgraded server now able to hand out enough work for all these GPUs?