Now disabled @ SETI@home: VLAR WUs not to GPUs |
![]() |
| log in |
Message boards : Number crunching : Now disabled @ SETI@home: VLAR WUs not to GPUs
1 · 2 · Next
| Author | Message |
|---|---|
|
SETI@home Beta Test : forum : 'VLAR WUs not to GPU' | |
| ID: 1016710 · | |
|
If you would like to test also, this is the URL of SETI@home Beta Test for your BOINC: http://setiweb.ssl.berkeley.edu/beta | |
| ID: 1016713 · | |
|
It's look like it work well on my system. | |
| ID: 1016928 · | |
|
Looks like it worked on mine so far...They take 20 hours on my CPU. If seti could do that much work on units it would really cut down server traffic. 10 day cache would be many. | |
| ID: 1017981 · | |
|
I made a quick look to your PC at SETI@home Beta Test.. | |
| ID: 1017997 · | |
I made a quick look to your PC at SETI@home Beta Test.. I changed the settings in seti beta to: SETI@home Enhanced: yes Astropulse: no Astropulse v5: no Is this correct? ____________ Official Abuser of Boinc Buttons... And no good credit hound! | |
| ID: 1018001 · | |
|
I looked to the preferences here, it should look similar at BETA: | |
| ID: 1018002 · | |
I looked to the preferences here, it should look similar at BETA: OK thats what I have, will give it a shot when severs are up. So far it only asked for CPU work when I let it ask. ____________ Official Abuser of Boinc Buttons... And no good credit hound! | |
| ID: 1018004 · | |
|
I guess you have too much GPU WUs from SETI@home DLed.. ;-) | |
| ID: 1018006 · | |
It's look like it work well on my system. And your experiences then there.. ;-) ____________ >Das Deutsche Cafe. The German Cafe.< | |
| ID: 1018007 · | |
|
Now enabled at SETI@home: 'VLAR WUs not to GPU' | |
| ID: 1018816 · | |
|
As for seeing the change - I just got a bunch marked vlar to the CPU. | |
| ID: 1018908 · | |
As for seeing the change - I just got a bunch marked vlar to the CPU. That's how Jeff said it would work. | |
| ID: 1018918 · | |
|
I still received 3 VLARs that were sent to My gpus, I'll be running rescheduler 1.9 until I see no need to run It anymore. | |
| ID: 1018922 · | |
I still received 3 VLARs that were sent to My gpus, I'll be running rescheduler 1.9 until I see no need to run It anymore. Jeff's post said it would not affect work that has already been split, but not sent out. Only the new work split will have this done to them. ____________ | |
| ID: 1018931 · | |
|
The splitters right now are cooking about 40 WU's a second and down to ~180000 | |
| ID: 1018938 · | |
I still received 3 VLARs that were sent to My gpus, I'll be running rescheduler 1.9 until I see no need to run It anymore. In addition to those which were probably split during the latest outage, VLARs have a 46.5 day deadline and reissues obviously can't change the WU name to have a .vlar added. There will be a possibility of getting such a reissue for at least several months, though they should be very rare within about 2 months. Joe | |
| ID: 1018958 · | |
|
I don't think it's because of the usage of the ReSchedule V1.9 tool.. | |
| ID: 1019808 · | |
I don't think it's because of the usage of the ReSchedule V1.9 tool.. It'll download them, if they are present in the feeder queue. The server modifications only prevent new VLAR tasks being added to that queue - old ones being resent will still be downloaded, as before. Are your VLARs all replication _2, _3 and above? They should be. | |
| ID: 1019813 · | |
|
The WUs have endings of .vlar_0 and .vlar_1 and are DLed for '608 cuda' (app_info.xml). | |
| ID: 1019816 · | |
Message boards : Number crunching : Now disabled @ SETI@home: VLAR WUs not to GPUs
| Copyright © 2013 University of California |