
Inhoudsopgave Seti@Home hitparades week 28
- DPC SETI@Home hitparade van 11 juli 2010
- DPC SETI@Home hitparade van 12 juli 2010
- DPC SETI@Home hitparade van 13 juli 2010
- DPC SETI@Home hitparade van 14 juli 2010 *
- DPC SETI@Home hitparade van 15 juli 2010
- DPC SETI@Home hitparade van 16 juli 2010
- DPC SETI@Home hitparade van 17 juli 2010
Wat is Seti@Home ?
Wat is SETI@home?
SETI@home is de naam van een wetenschappelijk experiment dat computers die via het internet met elkaar verbonden zijn, inzet om buitenaardse intelligentie op te sporen. U kunt hieraan deelnemen middels een gratis computerprogramma dat radiotelescoop-data download en analyseert.
BELANGRIJK wekelijkse server outage
New Outage Schedule
Starting next week our servers will be turned off for several days a week - initially, Tuesday through Thursday. This will allow us to devote more time to scientific development. 24 Jun 2010 21:56:37 UTC
NIEUWS UPDATE
10 Jul 2010 15:01:29 UTC
Things are looking OK from on this end. When the project was brought on line yesterday, none of the public facing servers were dropping TCP connections with the exception of the upload server. TCP drops on the upload server went to zero in about three hours.
The boinc database is keeping up. It was doing ~1000 queries per second mos of the day yesterday. It's down to about half of that now. Hiding those two threads (jobs limits and outage schedule) really helped. I'm not sure why those queries were hanging around so much. Number of posts? Waves of popularity?
The assimilators suddenly decided to start crashing on vader - a general protection exception in libc. I need to track that down. In the meantime, I moved the assimliators to bambi where they appear to run fine. Except for the known, occasional, memory leak which can, and did, bring a machine to it's knees. Another thing to track down. In the meantime (there are too many "meantimes"), I put an assimilator restarter in place on bambi. This method has been working well on vader. The assimilator queue is now draining.
Others have reported it, but I will report it again here. The job limits we started, and ran with, with yesterday were:
CPU 5 per processor
GPU 40 per processor
total (global) limit : 140
About an hour ago, I upped it just a bit to 6, 48, 150. I will remove all limits on Monday.
We will go for a better mix of files (and angle ranges) going into next week's server run.
[ Voor 0% gewijzigd door APClll op 15-07-2010 20:34 ]