.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 |
|---|---|
|
I have noticed that the .vlar units seem to be running about the same as non-.vlar units on my computer with a very slow GPU. I really can not tell about the credit.....my personal feeling is just get them over with and perhaps they will stop loading to the GPU. I also have many .vlar units loaded to my CPU so they do seem to be getting done. No errors on these noticed. | |
| ID: 1270993 · | |
I have noticed that the .vlar units seem to be running about the same as non-.vlar units on my computer with a very slow GPU. I really can not tell about the credit.....my personal feeling is just get them over with and perhaps they will stop loading to the GPU. I also have many .vlar units loaded to my CPU so they do seem to be getting done. No errors on these noticed. Mine are starting to run and I've cut back from 4 at at time to 3 at a time for my GTX 670 to reduce the run times. They run even better with 2 at a time and I may go to that and run them all tomorrow. As expected, DCF is getting messed up. Have plenty of tasks on hand, so no problem with a work fetch impact. I understand Richard's methodology for getting them resent to the CPU, but I don't feel confident with using software I'm not familiar with on a sensitive file. ____________ Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. | |
| ID: 1271000 · | |
|
No errors here either on cpu or gpu, but | |
| ID: 1271002 · | |
I have noticed that the .vlar units seem to be running about the same as non-.vlar units on my computer with a very slow GPU. I really can not tell about the credit.....my personal feeling is just get them over with and perhaps they will stop loading to the GPU. I also have many .vlar units loaded to my CPU so they do seem to be getting done. No errors on these noticed. I do not feel confident to do the necessary manual manipulations. By the way, I have gotten more .vlar's on my GPU today already. ____________ | |
| ID: 1271066 · | |
I have noticed that the .vlar units seem to be running about the same as non-.vlar units on my computer with a very slow GPU. I really can not tell about the credit.....my personal feeling is just get them over with and perhaps they will stop loading to the GPU. I also have many .vlar units loaded to my CPU so they do seem to be getting done. No errors on these noticed. Yes, I've got new ones today as well. They've been high replication numbers, like 1017893935 (_3) and 1017387288 (_4): people are starting to abort them. It was the first time I'd used Notepad++ as well, although I've seen it recommended on these boards before. You can practice the search with a simple 'find' (no replace), or use a copy of the file: nothing is changed on disk until you click 'save', and if you do that while BOINC is running, the file is going to get overwritten in a few seconds anyway - BOINC only ever reads client_state back in on restart. After a few runs, on five separate machines, I've got a pretty high degree of confidence in the editor - though I've printed out my own post and carry it round with me from machine to machine, to help me to do all the steps in the right order. The nice thing about N++ is that it keeps a history list of searches carried out. If you don't use it for anything else, the RegExp is still loaded ready for an instant search as soon as you open the file: even if you've used it for something else in between, the most you have to do is pick the right search off a drop-down list. | |
| ID: 1271072 · | |
I understand Richard's methodology for getting them resent to the CPU, but I don't feel confident with using software I'm not familiar with on a sensitive file. It was the first time I'd used Notepad++ as well, although I've seen it recommended on these boards before. You can practice the search with a simple 'find' (no replace), or use a copy of the file: nothing is changed on disk until you click 'save', and if you do that while BOINC is running, the file is going to get overwritten in a few seconds anyway - BOINC only ever reads client_state back in on restart. After a few runs, on five separate machines, I've got a pretty high degree of confidence in the editor - though I've printed out my own post and carry it round with me from machine to machine, to help me to do all the steps in the right order. Richard, you convinced me. Just got my first 20 resends w/o download. Didn't take long since you spent a lot of time paving the way - thanks for that and the confidence boost. Only hitch was that I had to turn on the "regular expression" (what ever that is) in Notepad++. I don't think I understand 10% of the settings in this app! Many thanks. Hope the lab finds the fix today. ____________ Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. | |
| ID: 1271095 · | |
|
| |
| ID: 1271112 · | |
|
This is annoying. I still get a whole lot of vlars for GPU. When will it end? | |
| ID: 1271156 · | |
|
I had contact with Eric and he said it should be fixed now. | |
| ID: 1271253 · | |
I had contact with Eric and he said it should be fixed now. Looks like I got these just before the hopeful fix. I am UTC -7. 8/13/2012 11:15:36 AM | SETI@home | [sched_op] Starting scheduler request 8/13/2012 11:15:36 AM | SETI@home | Sending scheduler request: To fetch work. 8/13/2012 11:15:36 AM | SETI@home | Reporting 43 completed tasks, requesting new tasks for NVIDIA 8/13/2012 11:15:36 AM | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices 8/13/2012 11:15:36 AM | SETI@home | [sched_op] NVIDIA work request: 42953.36 seconds; 0.00 devices 8/13/2012 11:15:36 AM | SETI@home | [sched_op] ATI work request: 0.00 seconds; 0.00 devices 8/13/2012 11:15:42 AM | SETI@home | Scheduler request completed: got 16 new tasks 8/13/2012 11:15:42 AM | SETI@home | [sched_op] Server version 701 8/13/2012 11:15:42 AM | SETI@home | Project requested delay of 303 seconds 8/13/2012 11:15:42 AM | SETI@home | [sched_op] estimated total CPU task duration: 0 seconds 8/13/2012 11:15:42 AM | SETI@home | [sched_op] estimated total NVIDIA task duration: 13951 seconds 8/13/2012 11:15:42 AM | SETI@home | [sched_op] estimated total ATI task duration: 0 seconds 8/13/2012 11:15:42 AM | SETI@home | [sched_op] Deferring communication for 5 min 3 sec 8/13/2012 11:15:42 AM | SETI@home | [sched_op] Reason: requested by project 8/13/2012 11:15:45 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.91.vlar 8/13/2012 11:15:45 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.16.vlar 8/13/2012 11:15:49 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.91.vlar 8/13/2012 11:15:49 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.16.vlar 8/13/2012 11:15:49 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.52.vlar 8/13/2012 11:15:49 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.70.vlar 8/13/2012 11:15:52 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.52.vlar 8/13/2012 11:15:52 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.70.vlar 8/13/2012 11:15:52 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.76.vlar 8/13/2012 11:15:52 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.80.vlar 8/13/2012 11:15:56 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.76.vlar 8/13/2012 11:15:56 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.80.vlar 8/13/2012 11:15:56 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.82.vlar 8/13/2012 11:15:56 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.26.vlar 8/13/2012 11:15:59 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.82.vlar 8/13/2012 11:15:59 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.26.vlar 8/13/2012 11:15:59 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.32.vlar 8/13/2012 11:15:59 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.38.vlar 8/13/2012 11:16:03 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.32.vlar 8/13/2012 11:16:03 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.38.vlar 8/13/2012 11:16:03 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.44.vlar 8/13/2012 11:16:03 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.78.vlar 8/13/2012 11:16:07 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.44.vlar 8/13/2012 11:16:07 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.78.vlar 8/13/2012 11:16:07 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.50.vlar 8/13/2012 11:16:07 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.37.vlar 8/13/2012 11:16:10 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.50.vlar 8/13/2012 11:16:10 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.37.vlar 8/13/2012 11:16:10 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.90.vlar 8/13/2012 11:16:10 AM | SETI@home | Started download of 02jl10aa.26155.24781.5.10.56.vlar 8/13/2012 11:16:14 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.90.vlar 8/13/2012 11:16:14 AM | SETI@home | Finished download of 02jl10aa.26155.24781.5.10.56.vlar ____________ | |
| ID: 1271260 · | |
|
I've cleared (hopefully) my last batch - getting quite a few from that same 02jl10aa 'tape' allocated direct to CPU in the process. Re-opened the floodgates to NV at about 21:20 UTC - I'll keep an eye open as the evening progresses. | |
| ID: 1271276 · | |
(...) Just a reminder... * Best regards! :-) * Sutaru Tsureku, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. * ____________ >Das Deutsche Cafe. The German Cafe.< | |
| ID: 1271636 · | |
|
I cached up with the best part of 1,000 WUs - maybe even more - on Tuesday, when the power maintenance work was announced. I've been allocated maybe 200 WUs since we came back this evening. No sign of any stray VLARs in either batch. | |
| ID: 1271653 · | |
|
I had 43 vlars on My PC and I don't do cpu wu's, so I aborted them, as they were taking at least 1 hour to do and I've got a GTX590, plus I was seeing slow downs as the cpu is an i5 750... | |
| ID: 1271859 · | |
|
I have been allowing 1 vlar wu at a time to be run along with 2 regular wu on my GTX-670. So far they are averaging around 48 minutes that way. | |
| ID: 1271890 · | |
|
| |
| ID: 1271922 · | |
|
In the congestion after the project came up, I had some "lost" VLAR tasks. The server timed them out on the next work request rather than send them to my Nvidia gpu, so that's a another good sign. I don't like the way that process works, but at least it is working again. I have received none for the gpu since the last fix. | |
| ID: 1271925 · | |
|
Since the problem was 'fixed' I have not had any new vlar's allocated to my GTX460. I have prioritised the 50 that I did have to get them crunched before the weekend and have been processing them 2 at a time. I currently have just 5 left. Even though my GTX460 has only 760MBytes memory this has caused no problems. They take 5 times as long as a normal WU (100 minutes instead of 20), but as long as I get 5x the credit I do not mind. | |
| ID: 1271986 · | |
|
My dual GTX550 Ti rig has been processing them 4 at a time and taking 3-5 times longer than then average work unit (depending on how many restarts they have to do with other work units going into high priority mode) but other than the longer run times they don't seem to be effecting the use of the rig in any way (BTW it's my daily hack). | |
| ID: 1272029 · | |
Message boards : Number crunching : .vlar WUs to NVIDIA GPUs (Problem Solved)
| Copyright © 2013 University of California |