It's a GTX460, so it can handle it OK, but still, thought the boys at the lab might like to know... It is fresh split work, as it is tagged _0.

Links to WU's:

666923166
666923160

---

Ooops, you're right. Looks like some customisations slipped out of the scheduler code while the servers were being swapped around. Let's hope we can attract the staff's attendtion to this thread when the time comes.

I got a third VLAR as well sent to the GPU, but it was old work before they were tagged as VLARs. I got it rescheduled before it started, so no worries there.

629356249

Also, wow these VLARs really slow down my video performance. Not too worried about it as I'm done for the night, just the first time I've had two running on the primary 460 at once...

---

.vlar WUs to GPU? This is since a few weeks also at SETI@home Beta Test.

---

I got a third VLAR as well sent to the GPU, but it was old work before they were tagged as VLARs. I got it rescheduled before it started, so no worries there.

629356249

Also, wow these VLARs really slow down my video performance. Not too worried about it as I'm done for the night, just the first time I've had two running on the primary 460 at once...

This is not a new .vlar WU. This is an old re-sent VLAR WU.
This is normal and could happen.
BOINC Rescheduler is still recommended.

The new .vlar WUs have .vlar in the name (at the end) and should go only to CPU.

---

I noticed some VLAR was sent to one of my rigs last night.
The poor thing was so crippled up by it, that I just decided to let whatever it was run it's course.
It has no GPU work left this morning, so it worked through them.
Not sure if they were first run or resends.

---

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

Ooops, you're right. Looks like some customisations slipped out of the scheduler code while the servers were being swapped around. Let's hope we can attract the staff's attendtion to this thread when the time comes.

I think everything is OK. The only vlar that I received was tagged correctly.

---

http://boincstats.com/signature/-1/user/18390/sig.png

The WUs were still tagged correctly, but it was my understanding that they shouldn't be scheduled to the GPU in the first place. Had I not been watching the rigs, I never would have noticed it.

---

Why are VLARs to the GPU a bad thing?

Why are VLARs to the GPU a bad thing?

VLAR's take something like 6 times as long to do as Normal AR tasks (on Cuda GPU's), and cause bad screen lag, sometimes driver restarts too,

Claggy

Exactly. My machine was barely usable while they were crunching. Luckily I was done on the computer for the night so I just let them run. The two units took nearly 2 hours to run, where as a normal WU runs in about 18min.

---