App installieren
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Anmerkung: This feature may not be available in some browsers.
Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
News update
- Ersteller Mike
- Erstellt am
Mike
Grand Admiral Special
- Mitglied seit
- 11.11.2001
- Beiträge
- 5.093
- Renomée
- 103
- Standort
- Bayern
- Aktuelle Projekte
- Einstein, Milkyway
- Lieblingsprojekt
- Seti
- Prozessor
- R7 1800X
- Mainboard
- Assus Crosshair 6 Hero
- Kühlung
- Noctua D15
- Speicher
- 16 GB Gskill 3200 CL14
- Grafikprozessor
- Sapphire RX 6600XT Nitro+
- SSD
- Samsung Nvme 970 EvoPlus 2TB + Samsung 960 Evo 500GB
- Netzteil
- Corsair Graphite 600D
- Betriebssystem
- Solus 4.5 Resilience
- Webbrowser
- Brave
HI
Von der Seti Seite.
greetz Mike
Von der Seti Seite.
November 30, 2005 - 22:30 UTC
So the master database merge is at a complete standstill. Unless everything suddenly works, we probably won't embark on this adventure until after the December 15th cutoff date for SETI@home Classic. It has become a programming/database nightmare where each fix or workaround brings forth another unexpected show-stopper.
Our server closet is in flux. The SETHI project (which uses SETI@home raw data to study hydrogen in our galaxy) recently bought a new dual opteron system (4GB RAM, 3TB drives) which we wanted to rack up in our closet, but kryten (the BOINC upload/download server) was actually in the way. So we rolled kryten into our secondary lab. But first we had to route a Cogent connection and a link to our internal gigabit switch into that lab. Also in this lab are isaac (the boinc.berkeley.edu web server among other things) and jocelyn (the BOINC database server), which we hope to move in the closet shortly after Classic is shut down.
When this happens, we'll be able to turn off sagan (the Classic data server) and get it out of the way, so we can remove a set of four A5000 (disk arrays attached to galileo which hold the now-defunct Classic master science database). And all this is just the beginning of what is shaping up to be a large-scale shell game.
We also updated DNS maps and URLs to continue balancing the web load as well as move the BOINC core client downloads off isaac and onto kryten. With the warning e-mails still being sent, the new core client downloads have been peaking out at 40 Mbit/sec. Since isaac, which handles these downloads, is on the campus network, this was adversely affecting others. So we moved all that traffic onto our Cogent link, which is now close to topping out at 100 Mbit/sec at any given time. All BOINC core client downloads, SETI@home science client downloads, SETI@home/BOINC workunits and SETI@home Classic workunits are all going out over our single Cogent connection. Of course, Classic activity will ramp down significantly over the coming weeks, so bandwidth constraints shouldn't be an issue.
greetz Mike
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
January 2, 2006 - 19:15 UTC
Happy New Year! The holiday season has been a bit of a headache, as several nagging problems kept the BOINC backend from running optimally. Luckily, most of us were around town and able to stop/start/reboot/kick things as needed to keep the project rolling as much as possible.
Most of the issues stem from an excessive load on the BOINC database. Remember that the BOINC database is the one that contains all the information pertaining to the distributed computing side of things: like users and teams, but also cursory workunit and result data for scheduling and sending/receiving purposes. We are still in the middle of the master database merge (see below for more information about that). This is an entirely different database that contains all the scientific products of SETI@home (both Classic and BOINC). So while we are busy merging the old and new scientific databases into one, this has no bearing on the problems people are having connecting to our servers, posting messages on the forums, etc. The merge process will be continuing for many weeks, in fact.
In a nutshell, the BOINC database issues started when we built up a large "waiting to assimilate" queue in mid-December. Then we got hit with, among other things, an influx of new users, a network outage beyond our control, a failed disk, a full disk, a spat of noisy workunits, and a database crash. All events were handled effectively, but the queues weren't draining as fast as we wished.
The sum of all this ended up being large, unweildy tables in the BOINC database, as old workunits and results weren't being purged and more entries were being inserted. All the backend processes that enumerate on these tables (the validator, the assimilator, the file_deleter, etc.) all slowed down. It got to the point that just doing a "select count(*)" on these tables would take 30 minutes, which is why we shut off the counts on the status page.
To help all this, we rebuilt some of the backend processes. Those who pay close attention may have noticed that workunit names have changed over the past week or so. It used to be a tape name followed by four dot-delimited numbers. Now there are five numbers. The new number (which is currently "1" for all workunits) is a scientific configuration setting. Having this number in the name saves us two expensive database reads to look up these configuration settings. This change vastly improved the assimilator throughput, but we were already mired in the problems listed above. Without this change, though, we would have been dead in the water, as the deleters would back up behind the assimilators. We would have then run out of workunit space, the splitters would halt, and no new work would be created.
Adding insult to injury, we found the feeder has some kind of bug in it. The feeder is the process that keeps a stash of results in shared memory that the scheduler reads to find out what to send to clients requesting work. Over time the feeder gets less and less able to keep a full stash. Eventually the feeder can't keep up with the scheduler's demand for results, and then clients get "no work available" messages. These clients retry quickly, and these extra connections cause stress on the server, which then starts dropping these connections. So every day or so we've been restarting the feeder to clear out its clogged shared memory segments and that temporarily improves connectivity. We're looking into it.
Since the last database compression/backup on Wednesday, we purged about 8 million results from the result table. So we decided to have another compression/backup outage today (Monday) to reap the benefit of a much smaller result table sooner than later.
http://setiathome.berkeley.edu/tech_news.php
Sir Ulli
edit sache sollte gelöst sein hoffe ich
Happy New Year! The holiday season has been a bit of a headache, as several nagging problems kept the BOINC backend from running optimally. Luckily, most of us were around town and able to stop/start/reboot/kick things as needed to keep the project rolling as much as possible.
Most of the issues stem from an excessive load on the BOINC database. Remember that the BOINC database is the one that contains all the information pertaining to the distributed computing side of things: like users and teams, but also cursory workunit and result data for scheduling and sending/receiving purposes. We are still in the middle of the master database merge (see below for more information about that). This is an entirely different database that contains all the scientific products of SETI@home (both Classic and BOINC). So while we are busy merging the old and new scientific databases into one, this has no bearing on the problems people are having connecting to our servers, posting messages on the forums, etc. The merge process will be continuing for many weeks, in fact.
In a nutshell, the BOINC database issues started when we built up a large "waiting to assimilate" queue in mid-December. Then we got hit with, among other things, an influx of new users, a network outage beyond our control, a failed disk, a full disk, a spat of noisy workunits, and a database crash. All events were handled effectively, but the queues weren't draining as fast as we wished.
The sum of all this ended up being large, unweildy tables in the BOINC database, as old workunits and results weren't being purged and more entries were being inserted. All the backend processes that enumerate on these tables (the validator, the assimilator, the file_deleter, etc.) all slowed down. It got to the point that just doing a "select count(*)" on these tables would take 30 minutes, which is why we shut off the counts on the status page.
To help all this, we rebuilt some of the backend processes. Those who pay close attention may have noticed that workunit names have changed over the past week or so. It used to be a tape name followed by four dot-delimited numbers. Now there are five numbers. The new number (which is currently "1" for all workunits) is a scientific configuration setting. Having this number in the name saves us two expensive database reads to look up these configuration settings. This change vastly improved the assimilator throughput, but we were already mired in the problems listed above. Without this change, though, we would have been dead in the water, as the deleters would back up behind the assimilators. We would have then run out of workunit space, the splitters would halt, and no new work would be created.
Adding insult to injury, we found the feeder has some kind of bug in it. The feeder is the process that keeps a stash of results in shared memory that the scheduler reads to find out what to send to clients requesting work. Over time the feeder gets less and less able to keep a full stash. Eventually the feeder can't keep up with the scheduler's demand for results, and then clients get "no work available" messages. These clients retry quickly, and these extra connections cause stress on the server, which then starts dropping these connections. So every day or so we've been restarting the feeder to clear out its clogged shared memory segments and that temporarily improves connectivity. We're looking into it.
Since the last database compression/backup on Wednesday, we purged about 8 million results from the result table. So we decided to have another compression/backup outage today (Monday) to reap the benefit of a much smaller result table sooner than later.
http://setiathome.berkeley.edu/tech_news.php
Sir Ulli
edit sache sollte gelöst sein hoffe ich
Zuletzt bearbeitet:
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
update
http://setiathome.berkeley.edu/tech_news.php
mfg
Sir Ulli
January 4, 2006 - 21:30 UTC
Well right now we're in the middle of another self-imposed outage to clear the pipes. The BOINC database compression on Monday helped a bunch - enough that the final troublesome queues were draining, but not nearly as fast as we would like.
Here are some numbers: Normally the entire BOINC database, when unloaded to an uncompressed ASCII file, is about 17GB. This is largely due to the huge workunit/result tables. Because of assimilator/file deleter issues, by December 21 the database swelled up to 26GB. On December 28 it was 31GB. Unable to purge old workunits and results, our database ended up nearly double its normal size! No wonder we were in a world of hurt.
After the new year we recovered a bit, and the compression on Monday brought it back down to 26GB. But we still had this annoying backlog of a million workunits and four million results, and until we got those purged, we weren't going to get any smaller.
This morning we turned off the scheduler to allow these queues to finally drain. We estimate it will take until tomorrow morning to clear everything out once and for all. Better to just bite the bullet and fix it rather than watch and hope for improvement during the coming weeks. When the queues all hit zero, we'll do one more quick database compression/backup and get back to work.
http://setiathome.berkeley.edu/tech_news.php
mfg
Sir Ulli
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
January 5, 2006 - 23:30 UTC
We're back on line after a day-and-a-half long outage during which we were able to clear out enough of our BOINC database to get us back to the same levels as in early December. Of course, there's going to be a painful period as all the BOINC clients clog our servers with demands for work. This will push through eventually as it always has. Meanwhile the master database merge is going along swimmingly - the result and signals tables are copying over much faster than expected.
http://setiathome.berkeley.edu/tech_news.php
mfg
Sir Ulli
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
wenn das mal nicht wieder was mit Cogent zu tun hat....
mfg
Sir Ulli
mfg
Sir Ulli
Shaidar
Lieutnant
wenn das mal nicht wieder was mit Cogent zu tun hat....
mfg
Sir Ulli
Servus,
könntest du "Cogent" mal etwas näher präzisieren, hab
nicht die geringste Ahnung wer oder was das sein könnte
gruß Shaidar
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
Cogent...
schau mal hier
http://www.heise.de/newsticker/search.shtml?T=cogent&button=los!
btw Cogent ist der Provider von Berkeley
mfg
Sir Ulli
schau mal hier
http://www.heise.de/newsticker/search.shtml?T=cogent&button=los!
btw Cogent ist der Provider von Berkeley
mfg
Sir Ulli
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
January 16, 2006
It looks like we may be experiencing local SSL network problems again. If so, this will likely be fixed tomorrow. Today is a university holiday. In the meantime there will be intermittent problems contacting the scheduling server.
http://setiathome.berkeley.edu/index.php
es ist mal wieder soweit
17.01.2006 23:41:35||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
17.01.2006 23:41:35|SETI@home|Temporarily failed upload of 24my03ab.1783.8976.15918.1.254_2_0: system I/O
17.01.2006 23:41:35|SETI@home|Backing off 18 minutes and 7 seconds on upload of file 24my03ab.1783.8976.15918.1.254_2_0
nur beim Beta Project gibt es wohl keine Probs
mfg
Sir Ulli
gruenmuckel
Grand Admiral Special
- Mitglied seit
- 17.05.2001
- Beiträge
- 29.626
- Renomée
- 1.743
- Standort
- Gerry-Weber - Stadt
- Aktuelle Projekte
- Collatz, Milkyway, POEM
- Lieblingsprojekt
- POEM & QMC etwa gleich
- Meine Systeme
- C2Q8400@3,2Ghz I7-3770K C2DE6750
- BOINC-Statistiken
- Mein Laptop
- Dell Studio 1749 @ work / Medion Erazer X7826 @ play
- Prozessor
- Intel Core i7 6700K
- Mainboard
- Asrock Z270 Extreme4
- Kühlung
- EKL Alpenföhn Matterhorn PURE
- Speicher
- 1x 16GB G.Skill Aegis DDR4-2400 DIMM CL15-15-15-35
- Grafikprozessor
- Sapphire AMD Radeon RX 480 NITRO 8GB
- Display
- LG Ultrawide 21:9 "29UM67-P & FullHD Packard-Bell-TV
- SSD
- 1TB 840 EVO, Mushkin Reactor1TB, Sandisk Extreme 480GB
- HDD
- 1xMD04ACA400, 2x Seagate Archive 8TB
- Optisches Laufwerk
- LG GH22NS40, Sony Optiarc BD-5300S Blu-Ray Brenner
- Soundkarte
- Creative Recon3D PCIe
- Gehäuse
- Corsair Obsidian 650D (2x 140mm Vegas Duo + 1x 120mm Vegas Trio)
- Netzteil
- Corsair RM650i
- Betriebssystem
- Windows 7 64 SP1
- Webbrowser
- Firefox aktuelle Version
- Verschiedenes
- Hauppauge WinTV USB , Scythe Kaze Master Ace Lüfte
- Schau Dir das System auf sysprofile.de an
Das war eng!
January 24, 2006 - 22:00 UTC
Well, we had an outage today to move some disks around. A replacement workunit storage server enclosure arrived and it should have been a simple disk exchange. But things kind of exploded and we didn't even get to that.
To shut down the workunit storage server we had to first unmount it on all the splitter/download machines. But koloth and kryten were having all kinds of mounting troubles. Eventually we had to reboot kryten to clear the pipes. But then it took 45 minutes to shut down for reasons we are still unclear about. We didn't want to power cycle the thing as the result storage disks attached to it were quite busy doing something.
Eventually the disks fell quiet, but then nothing happened for a good 15 minutes. We gave in and powered it down. We flipped the switch, but it didn't power back up. We tried again, and then smoke and sparks came out from around the power cord.
Uh oh.
The cord was slightly melted. We threw it out, got a new cord and a better surge protector in place, and kryten powered up (phew) but died within 15 seconds. Apparently we had a bad power supply.
By some divine luck we happened to have one spare E3500 power supply kicking around in the basement. It was an easy replacement and then kryten powered up just fine. That was a major relief, as we don't really have a good backup server for kryten at this point in time. After careful inspection and remounting everything we eventually came back on line.
Sir Ulli
Grand Admiral Special
- Mitglied seit
- 06.02.2002
- Beiträge
- 14.440
- Renomée
- 202
- Standort
- Bad Oeynhausen
- Aktuelle Projekte
- Seti, Spinhenge
- Lieblingsprojekt
- Seti, Spinhenge, ich war vor Ort
- Meine Systeme
- Athlon64 X2 4.400, Imhell Quad 6.600
- Mein Laptop
- HP 530
- Prozessor
- Imhell Quad 6.600 at 3.240 8 x 405
- Mainboard
- Aus P5K Rev 2.1
- Kühlung
- Thermalright SI-128 SE Papst 120 at 1.200
- Speicher
- 2 x A-DATA 4 GB DDR2-800 Kit 4,4,4,12
- Grafikprozessor
- Asus 8.500 GT SILENT/HTP/256M
- Display
- Samsung SyncMaster 2232BW 22 Zoll TFT
- HDD
- Western Digital WD10EACS 1 TB
- Optisches Laufwerk
- Samsung SH-S203P Sata
- Soundkarte
- onboard
- Gehäuse
- CS601 mit 2extra Päpsten at 9 Volt
- Netzteil
- Fortron 350 Watt
- Betriebssystem
- Windows7 Home Premium
- Webbrowser
- Mozilla Firefox
mein cache ist gross genug, merke diese Kleinigkarten gar nicht mehr...
mfg
Sir Ulli
mfg
Sir Ulli
Ähnliche Themen
- Antworten
- 1
- Aufrufe
- 226
- Antworten
- 0
- Aufrufe
- 283
- Antworten
- 0
- Aufrufe
- 196
- Antworten
- 0
- Aufrufe
- 433