.vlar WUs to NVIDIA GPUs (Problem Solved) |
![]() |
| log in |
Message boards : Number crunching : .vlar WUs to NVIDIA GPUs (Problem Solved)
Previous · 1 · 2 · 3 · 4 · 5 · Next
| Author | Message |
|---|---|
|
Found 3 more vlar tasks sent to the GPU on 2 other pc's. 2 were sent in a request of 23:12 CET and that would be before the new scheduler was active, the third one was received after a request at 4:39 CET. | |
| ID: 1269911 · | |
|
| |
| ID: 1269912 · | |
|
And it gets worse: this host just received 6 vlars, the request is from 10:59 CET (8:59 UTC). | |
| ID: 1269919 · | |
And it gets worse: this host just received 6 vlars, the request is from 10:59 CET (8:59 UTC). John - that host is running Linux. I'm not 100% sure whether the 'no VLAR to NV' policy used to be applied on all platforms, or just Windows. Have you ever seen VLARs before this? I'll mention it in my next report to Eric, when the lab opens. | |
| ID: 1269924 · | |
John - that host is running Linux. I'm not 100% sure whether the 'no VLAR to NV' policy used to be applied on all platforms, or just Windows. Have you ever seen VLARs before this? Richard, I have 3 Linux hosts and before this, I never saw tasks with the vlar suffix going to the GPU | |
| ID: 1269928 · | |
John - that host is running Linux. I'm not 100% sure whether the 'no VLAR to NV' policy used to be applied on all platforms, or just Windows. Have you ever seen VLARs before this? Thanks, I think that confirms that the previous policy applied cross-platform. I wasn't sure, because of course the project only has stock applications for Windows. | |
| ID: 1269930 · | |
|
The fixed scheduler might be catching .0 and .1 vlars, but apparently not resends. Example | |
| ID: 1270216 · | |
The fixed scheduler might be catching .0 and .1 vlars, but apparently not resends. Example Unfortunately not. I got 25ap11ac.19317.20930.3.10.218.vlar_1 sent to my laptop this morning. | |
| ID: 1270319 · | |
|
My BOINC still getting .vlar WUs for the NVIDIA GPU... | |
| ID: 1270361 · | |
|
And I haven't seen VLAR WUs ATI-GPU for days, most if not all, are ~0.4ARWUs. | |
| ID: 1270383 · | |
|
| |
| ID: 1270574 · | |
|
Hello just got a bunch of _vlar2: | |
| ID: 1270706 · | |
Hello just got a bunch of _vlar2: I think if you read the posts in this thread, you will have most of your questions answered. This problem has nothing to do with preferences or your BOINC version. ____________ | |
| ID: 1270710 · | |
Richard is working on 'how to get the server to resend the VLAR to the CPU' instructions, which he will post once he's confirmed the procedure works reliably. * Make backup copy of all .vlar datafiles * Restore all .vlar datafiles Does this mean "ALL" meaning also those .vlar datafiles that are already assigned to CPU? ____________ | |
| ID: 1270711 · | |
* Make backup copy of all .vlar datafiles At the time I wrote that, we were hoping that Eric would be able to restore the status quo quickly and easily, so we wouldn't need to apply the treatment more than once. What I do is to sort the file list in Windows Explorer on the 'Type' column (in 'detail' view). That groups all "VLAR Files" together, and I can right-click them into whatever archiver I have handy - WinZip, 7-zip, WinRAR, or plain old 'compressed folder'. After the BOINC restart step, files for the results you're deleted will have disappeared from the list. When you copy files back from the archive, the missing files will drop straight back in, but the old files, still being present, will prompt Windows to say 'do you want to overwrite this file?', or something like that. It really doesn't matter, but you may as well say no to all, to save wear and tear on the disk. But let Windows do the decision-making - it's really not worth the effort to pick them out individually yourself. If your machine is fast enough to have lots of VLAR files that need treating, it should be able to handle the backup process quickly too. [hint: you could save a few seconds of shutdown time by making the VLAR file archive before you stop BOINC - that's OK] Just don't apply this process to the .vlar_0_0 files generated while the CPU is working on the tasks you processed last time. And don't delete the <result> blocks for CPU tasks (version 603, no plan_class) - see the dicussion on Notepad++ and regular expressions earlier in this thread. | |
| ID: 1270730 · | |
Does this mean "ALL" meaning also those .vlar datafiles that are already assigned to CPU? Actually not, but it's probably a lot easier to just backup all .vlar files, and skip those that are there, when restoring them. However "Edit client_state.xml: remove all '<result>' blocks for .vlar tasks" applies only to those, that are assigned to GPU, i.e. version 608, 609 or 610 (see also the NPP discussion above on how to easily find and remove those). EDIT: I really need to learn to hit F5 before posting to a thread. ____________ . | |
| ID: 1270736 · | |
|
I didn't notice any VLARs assigned to my CUDA GPUs when this issue was first raised, but now I'm starting to get them with increasing frequency. I'm not complaining at all, just noting that the issue appears to be ongoing. | |
| ID: 1270741 · | |
* Make backup copy of all .vlar datafiles I got it regarding the backup. The .vlar_0_0 was however a new point. Will all the active tasks get an extra _0 after the filename? ____________ | |
| ID: 1270743 · | |
* Make backup copy of all .vlar datafiles To explain about the names: I'll take my WU 1045795612 as an example. The workunit is '25ap11ac.2053.25024.4.10.250.vlar', and that's the name of the file that both I and my wingmate have downloaded. My Task is '25ap11ac.2053.25024.4.10.250.vlar_0', and my wingmate's task is '25ap11ac.2053.25024.4.10.250.vlar_1'. My computer will create a result file '25ap11ac.2053.25024.4.10.250.vlar_0_0', and my wingmate will create '25ap11ac.2053.25024.4.10.250.vlar_1_0' - those two files will be uploaded to the server and compared. So you may see any variation of _x_0 for tasks which are running. They are created as soon at the job starts to run (with a copy of the telescope recording information from the header of the WU file), but added to at intervals during the run, as signals are found. It would be safe to back them up and restore them while BOINC is stopped, but not safe while BOINC is running - the file might have changed between backup and restore. | |
| ID: 1270750 · | |
Hello just got a bunch of _vlar2: I see you are using GTX 560ti cards. I recently installed one of these and was wondering just what king of problems you are running into with vlar work units? Mine is set to run three WUs at one time and haven't had any troubles so far and they run faster on the gpu than on the cpu. I'm looking for any problems that I may encounter so I'll be prepared with a solution. | |
| ID: 1270964 · | |
Message boards : Number crunching : .vlar WUs to NVIDIA GPUs (Problem Solved)
| Copyright © 2013 University of California |