Message boards :
Number crunching :
Now disabled @ SETI@home: VLAR WUs not to GPUs
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
The WUs have endings of .vlar_0 and .vlar_1 and are DLed for '608 cuda' (app_info.xml). You're right, this .VLAR Wu has been sent to the GPU, maybe because it's a resend? (Edit: i now see you have others sent to the GPU, that aren't resends) http://setiathome.berkeley.edu/workunit.php?wuid=636108071 Claggy |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
The WUs have endings of .vlar_0 and .vlar_1 and are DLed for '608 cuda' (app_info.xml). Interesting. This sounds like a bug: more evidence please, guys. I wonder whether the new scheduler rules for "Don't send .vlar to CUDA" have a hidden exception "except for anonymous platform" - wouldn't be the first time that's happened with DA's code. We're still waiting for debugged server-DCF for anonymous platform, remember. |
Sutaru Tsureku Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5 |
The WUs have endings of .vlar_0 and .vlar_1 and are DLed for '608 cuda' (app_info.xml). This is a .vlar_2 WU. Strange, I have this WU not in my BOINC. So I guess it's a ghost WU. I have current 41 .vlar_0 and .vlar_1 WUs for GPU in my BOINC (So this are new ones). So later I need to use the ReSchedule tool for to protect my GPU for VLAR WUs. |
John Neale Send message Joined: 16 Mar 00 Posts: 634 Credit: 7,246,513 RAC: 9 |
Sutaru, you run optimised ("anonymous") apps at SETI Beta. Did you observe this behaviour there? |
Sutaru Tsureku Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5 |
Sutaru, you run optimised ("anonymous") apps at SETI Beta. Did you observe this behaviour there? At SETI@home Beta Test the '.vlar WUs not to GPU' ran well with app_info.xml file. But there I have 609 and cuda23 entries in my app_info.xml file. |
JohnDK Send message Joined: 28 May 00 Posts: 1222 Credit: 451,243,443 RAC: 1,127 |
I've not been getting any .vlars for my GPU, has anybody else (except Sutaru)? |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
I've not been getting any .vlars for my GPU, has anybody else (except Sutaru)? I was away for the weekend, but I've just looked through my BoincView logs: no sign of any .vlar WU being downloaded on any of my CUDA boxes (they only fetch GPU work from SETI - CPUs are kept busy by other projects). Doesn't mean that the project server code hasn't changed today, of course. |
perryjay Send message Joined: 20 Aug 02 Posts: 3377 Credit: 20,676,751 RAC: 0 |
I've only got 14 of the VLAR marked WUs but they all were assigned to my CPUs. I've also got 2 non-marked VLARs but they also went to my CPUs. My reschedule v1.9 is starting to feel neglected. :-) PROUD MEMBER OF Team Starfire World BOINC |
Geek@Play Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 |
All my vlar's are properly assigned to the cpu's. I have several that are _2 reissues and still to cpu's. http://setiathome.berkeley.edu/workunit.php?wuid=636077927 http://setiathome.berkeley.edu/workunit.php?wuid=635619180 Both to cpu's as required. Boinc....Boinc....Boinc....Boinc.... |
Harri Liljeroos Send message Joined: 29 May 99 Posts: 4092 Credit: 85,281,665 RAC: 126 |
I've got four of these too on my host. All .vlar_0 and .vlar_1. And I also have app_info for 6.08 and cuda23. This one 01jn10ab.19594.7429.16.10.176.vlar was sent also to a standard 6.09 application. |
Miep Send message Joined: 23 Jul 99 Posts: 2412 Credit: 351,996 RAC: 0 |
ok, so to conclude, while most people don't see vlar marked tasks on their GPU a few seem to have been slipping through the net. I checked a few of Harri's vlar to GPU WUs and in most cases both tasks have been sent to a GPU. So some vlar issued to stock 6.09 and some to ap - what are you running Sutaru? 6.09 but in app_info? And Harri's wingman to the 6.09 is running V12. Doesn't look like much of a pattern. Carola ------- I'm multilingual - I can misunderstand people in several languages! |
Sutaru Tsureku Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5 |
At SETT@home Beta Test I had 609_cuda23 entries in my app_info.xml file, with stock 6.09 CUDA app. And everything fine. Here at SETI@home I have 608_cuda entries in my app_info.xml file, with stock 6.09 CUDA app. And my BOINC get .vlar_0 and .vlar_1 WUs for GPU. EDIT: BTW. Harri, you need to delete the '/' at the end of your URL for well redirection. |
Geek@Play Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 |
Is it possible that some are using the redistribute and inadvertantly move VLAR from CPU to GPU while trying to keep GPU's busy. Boinc....Boinc....Boinc....Boinc.... |
Harri Liljeroos Send message Joined: 29 May 99 Posts: 4092 Credit: 85,281,665 RAC: 126 |
@Sutaru Thanks for pointing that extra "/" out, cut and paste fault. Unfortunately can't edit it anymore. @Miep Actually mine is the V12 and my wingman has the 6.09. And he got it first. |
Miep Send message Joined: 23 Jul 99 Posts: 2412 Credit: 351,996 RAC: 0 |
Is it possible that some are using the redistribute and inadvertantly move VLAR from CPU to GPU while trying to keep GPU's busy. No, website shows what's been issued to, you need to check the task itself to see where it's been processed (after is has come in). Sorry Harry :) Misread your post as yours being the 6.09, whilst you were actually pointing out that the second task had gone to GPU as well and to stock on top. Carola ------- I'm multilingual - I can misunderstand people in several languages! |
Miep Send message Joined: 23 Jul 99 Posts: 2412 Credit: 351,996 RAC: 0 |
Problem found - see Matt's post. Can't expect vlar marked tasks not to end up on the GPU if the discriminating code is not turned on ;) Carola ------- I'm multilingual - I can misunderstand people in several languages! |
Sutaru Tsureku Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5 |
Thanks for the hint. Ohh.. strange.. At SETI@home Beta Test it worked very well.. EDIT of the title of this thread from 'Now enabled @ ..' to 'Now disabled @ ..'. |
Donald L. Johnson Send message Joined: 5 Aug 02 Posts: 8240 Credit: 14,654,533 RAC: 20 |
Problem found - see Matt's post. As I read Matt's note, the VLAR change was only turned off for a couple of hours on Monday, so he fixed it after he became aware of it. Still, it was long enough that some folks got VLARs sent to their GPUs. And we will still have resends of VLARs split before the changes went in, probably for a couple of months. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.