| Author |
Message |
|---|
 Matt LebofskyVolunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 1 Mar 99
Posts: 1375
Credit: 74,079
RAC: 0
|
|
So it's official: you can now run SETI@home on your NVIDIA GPU. Of course they're still working out the kinks, and it has yet to be seen what effects (immediate and long term) this will have on our servers and known bottlenecks. Such things are quite unpredictable, given the dizzying long list of variables.
In order to keep our bandwidth from going bonkers due to all the new client downloads, we employ the use of Coral Cache. This is all well and good, except that some ISPs out there firewall http redirects, which means a tiny subset of users cannot download these new clients. This is unfortunate, as we have no choice because we can't handle the new client downloads ourselves. So these few users will suffer a bit until we can remove such caching.
Our replica server never did recover from the outage yesterday, causing stats of various kinds to be jammed for the past day or so. This morning we found scary log messages and we couldn't even shut mysql down gracefully, so we had to kill the process and reboot the machine. It's been in really slow recovery mode all day. When finished there's a good chance it'll be out of sync from the master and will have to be rebuilt from scratch anyway. Sigh. In the meantime, I'm pointing all queries at the master, which is loading it down a bit and causing us some minor grief (running out of work to send, for example).
- Matt
____________
-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude |
|
|
|
|
|
Thanks for the Updates.
... and I have my fingers crossed in hope that the replica can quickly get back to it's updates... |
|
|
|
|
|
Thanks for the Updates.
Will a CUDA version of SETI be coming out for Linux? |
|
|
ML1Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 7109
Credit: 3,681,270
RAC: 933
|
So it's official: you can now run SETI@home on your NVIDIA GPU. Of course they're still working out the kinks, ...
Great stuff and hopefully there'll be a flurry of bug-fixes to keep pace with what is found.
Regardless of a few squeals, it must be well worth even a baptism of fire. (OK, so here's hoping for not too much of the fire and brimstone and burnt bits!)
In order to keep our bandwidth from going bonkers due to all the new client downloads, we employ the use of Coral Cache. This is all well and good, except that some ISPs out there firewall http redirects, ...
Either of "Websense" and (long time) buggy Windows name servers can also block things.
The Coral Cache is a rather interesting system. See:
PlanetLab
Coral Content Distribution Network
... and very apt for Boinc to be using it!
... causing us some minor grief (running out of work to send, for example).
Hopefully a positive future occurrence when the GPU efficiency is improved ;-)
Hope you don't suffer too many new headaches with the yet more new stuff.
Happy fast crunchin',
Regards,
Martin
____________
Mandriva Linux A user friendly OS!
See new freedom Mageia2
The Future is what We make IT (GPLv3) |
|
|
|
|
|
@ Matt:
I got the Seti@home 6.06-CUDA app yesterday from the Beta Test area, and quickly crunched 1 WU with it yesterday. BUT me and others aren't able to upload completed WU results from our Seti@home Beta Test projects, as noted in this growing thread:
http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=1460
I don't know if the upload problem is for Cuda-only or also for AP-5.00 WUs (I'm crunching 2 AP-5.00 WUs, only 30% done after 9+ hrs cputime). Anyway, could you/someone look into the upload problem please.
____________
Sabertooth Z77, i7-3770K@4.2GHz, GTX680, W8Pro x64
P5N32-E SLI, C2D E8400@3Ghz, GTX580GT/1536MB, Win7SP1Pro x64 & PCLinuxOS2013
  |
|
|
|
|
I don't know if the upload problem is for Cuda-only ....
I'm pretty sure it's a generic problem affecting the whole upload server: I've got a whole lot of v6.03 CPU tasks trying to upload. It's BOINC which does the uploads (not the CUDA app, the CPU app, or the AP app), and according to one user BOINC is reporting a 503 "Service Temporarily Unavailable" error.
The bad news is, Matt switched his fourth working day of the week from Thursday to Friday a little while back, so he probably won't be able to read or act upon this information until tomorrow. |
|
|
|
|
|
Richard, thanks for your reply.
A short time ago, one of my two (Beta Test project) AP-5.00 WUs finished but neither it nor the (Beta Test project) 6.06-cuda WU that finished yesterday will upload. However, 2 recently completed (Non-Beta SETI@home project) MB WUs finished crunching and both DID upload successfuly. Here's excerpt from BOINC Manager v6.4.5 Message log:
12/18/2008 2:18:03 PM|SETI@home|Computation for task 14no08ac.7403.6386.9.8.155_1 finished
12/18/2008 2:18:03 PM|SETI@home|Starting 14no08ac.719.13748.12.8.198_1
12/18/2008 2:18:03 PM|SETI@home|Starting task 14no08ac.719.13748.12.8.198_1 using setiathome_enhanced version 528
12/18/2008 2:18:05 PM|SETI@home|Started upload of 14no08ac.7403.6386.9.8.155_1_0
12/18/2008 2:18:17 PM|SETI@home|Finished upload of 14no08ac.7403.6386.9.8.155_1_0
12/18/2008 2:18:48 PM|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
12/18/2008 2:18:53 PM|SETI@home|Scheduler request completed: got 0 new tasks
12/18/2008 2:19:35 PM|SETI@home|Started upload of 02dc08ad.7356.217693.11.8.254_0_0
12/18/2008 2:19:44 PM|SETI@home|Finished upload of 02dc08ad.7356.217693.11.8.254_0_0
12/18/2008 2:20:43 PM|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
12/18/2008 2:20:48 PM|SETI@home|Scheduler request completed: got 0 new tasks
12/18/2008 2:21:47 PM|SETI@home Beta Test|Started upload of 03no08aa.4033.2526.5.11.133_0_0
12/18/2008 2:21:47 PM|SETI@home Beta Test|Started upload of ap_03no08aa_B2_P0_00225_20081217_19478.wu_1_0
12/18/2008 2:22:51 PM|SETI@home Beta Test|Temporarily failed upload of ap_03no08aa_B2_P0_00225_20081217_19478.wu_1_0: HTTP error
12/18/2008 2:22:51 PM|SETI@home Beta Test|Backing off 2 hr 10 min 50 sec on upload of ap_03no08aa_B2_P0_00225_20081217_19478.wu_1_0
12/18/2008 2:23:33 PM|SETI@home Beta Test|Temporarily failed upload of 03no08aa.4033.2526.5.11.133_0_0: HTTP error
12/18/2008 2:23:33 PM|SETI@home Beta Test|Backing off 41 min 3 sec on upload of 03no08aa.4033.2526.5.11.133_0_0
____________
Sabertooth Z77, i7-3770K@4.2GHz, GTX680, W8Pro x64
P5N32-E SLI, C2D E8400@3Ghz, GTX580GT/1536MB, Win7SP1Pro x64 & PCLinuxOS2013
|
|
|
|
|
|
. . . Thanks for the Updates Matt
- Berkeley - as usual nice work
~ kinks always have a way of workin' themselves out eh ~
____________
 BOINC Wiki . . .
Science Status Page . . .
|
|
|
|
|
|
[quote]Richard, thanks for your reply.
A short time ago, one of my two (Beta Test project) AP-5.00 WUs finished but neither it nor the (Beta Test project) 6.06-cuda WU that finished yesterday will upload. However, 2 recently completed (Non-Beta SETI@home project) MB WUs finished crunching and both DID upload successfully. Here's excerpt from BOINC Manager v6.4.5 Message log:
[snip]
Please note that Seti beta is a different project and that, while running on the same hardware, (in some cases) the processes involved are specific to beta - they (supposedly) don't interfere with the main project and vice-versa.
____________
.
  |
|
|
