And Eric has the fix in now. GPU cards should not be getting any more VLARs.

Meow.

Crap. I like them on my HD7870. I wish they could allow vlar's going to ATI cards, but not to Cuda cards.

There are others that have expressed that, but ATI users are in the minority, and since it would take a code rewrite from DA above, I think, to add the additional selection, it has never been done. Since the nVidia users far outweigh ATI users, the project does what it has to do to avoid crippling a large percent of their user base.

I think you would have to petition DA in another forum to ask for a change.

Meow.

And some have expressed similar machine usability concerns with them on ATI's too, so I think it's a bit of a system dependant case. They remain actively distributed to at least NV GPUs on beta for development/research purposes. I suspect at least some portion of the (legitimate IMO) concerns are RAC/Credit related, which will only reduce/disappear when the time estimate system is improved. The remaining machine usability related issues then only come with further application development.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

It's not a big deal. However, it was fun while it lasted :-)
MY HD7870 is screaming through my last 6 vlar's now, and after that I guess I will never see vlar's again, since I do not run MB on my CPU.

mmmm, never say never. Some sortof opt in tickbox wouldnt seem that big of a deal to me', but probably before such an extension Eric might be concerned about preventing a repeat of damage to things that already work.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I wondered why my whole computer was running like a bag of goo since yesterday. VLAR CUDA work units not only were taking 1.5 hours to complete, but the system was unusably slow with a screen updates, even as simple as scrolling browser window, hanging... watching any video was a hopeless mass of chunky pixel artifacts. CPU usage which usually is rock-steady at 99.5%-100% with a flat ceiling was spiky/choppy and below 90%. They really brick the whole works, so I aborted the lot of them.

---

The vlars can be sent to my nvidia any time from now on. I made a bug to the code that checks the AR and assigns a char zero to null whenever ar < z.

setiathome enhanced x41zc, Cuda 6.50 special

Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 128k elements.
Work Unit Info:
...............
WU true angle range is :  0.008647
SIGSEGV: segmentation violation
Stack trace (8 frames):
../../projects/setiathome.berkeley.edu/setiathome_x41zc_x86_64-pc-linux-gnu_cuda65[0x4ae0a0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfc90)[0x7f2cc7e6bc90]
../../projects/setiathome.berkeley.edu/setiathome_x41zc_x86_64-pc-linux-gnu_cuda65[0x41654e]
../../projects/setiathome.berkeley.edu/setiathome_x41zc_x86_64-pc-linux-gnu_cuda65[0x423275]
../../projects/setiathome.berkeley.edu/setiathome_x41zc_x86_64-pc-linux-gnu_cuda65[0x42def4]
../../projects/setiathome.berkeley.edu/setiathome_x41zc_x86_64-pc-linux-gnu_cuda65[0x406a26]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f2cc4618ec5]
../../projects/setiathome.berkeley.edu/setiathome_x41zc_x86_64-pc-linux-gnu_cuda65[0x40a027]

Exiting...

</stderr_txt>
]]>

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

lol, naughty man.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I wondered why my whole computer was running like a bag of goo since yesterday. VLAR CUDA work units not only were taking 1.5 hours to complete, but the system was unusably slow with a screen updates, even as simple as scrolling browser window, hanging... watching any video was a hopeless mass of chunky pixel artifacts. CPU usage which usually is rock-steady at 99.5%-100% with a flat ceiling was spiky/choppy and below 90%. They really brick the whole works, so I aborted the lot of them.

Yup... brick it is the correct term.
I think the kitties have managed to work through the mess.
I had a power outage in the meantime which managed to muck up a whole lotta things.

Let's just say things are better now........

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

And some have expressed similar machine usability concerns with them on ATI's too, so I think it's a bit of a system dependent case.

I definitely remember VLAR tasks causing issues on both NV and ATI/AMD GPUs before the filtering was implemented, in terms of GUI unresponsiveness and other annoying performance issues. This time around my GPUs may be recent or powerful enough to not be as badly affected (but still noticed the occasional problem), but I still would not want VLAR tasks on either type of GPU. I confirm, as was the case previously, that AMD GPUs are not as adversely affected by VLAR tasks as NV GPUs are in terms of performance slow-down, but they still are to some degree.

---

Soli Deo Gloria