• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Technical News and SETI@home daily Team-stats for 13 - 14.07.2008.

R

Rattledagger

Elite Member
Returning (Jul 14 2008)

So the second half of last week was spent trying to figure out why our database server was so painfully slow. Bob, Jeff, Eric, and I were scratching our heads, trying this and that to diagnose and fix this mysterious problem. Everything was fine before the Tuesday outage, nothing changed during the outage, but upon restarting the project we couldn't handle very much load.

We were quick to blame mysql, as it has had random episodes in the past of secretive bookkeeping causing us grief. We ruled this out. We started blaming the "credited job" table which is growing infinitely. This is the table keeping track of which user did which workunit. We do nothing but insert into this table (no random access selects), so why would that be a problem? Nevertheless we turned off inserts (back to writing similar info to flat files for later parsing) to no avail.

Maybe it was hardware? Did a disk fail? Is a disk about to fail? We ruled all that out as well, which brought the focus back on mysql with dozens of server tuneables that we tweaked for various reasons over the years. Did we go too far with some of those variables? We convinced ourselves that wasn't it.

Of course on hindsight the ultimate solution seems obvious: the filesystem where all the data is kept. Just because the hardware seems okay, and I/O rates are normal, doesn't mean the filesystem is happy. And the focus was back on "credited job" as this table is constantly growing and therefore a big ol' file - much bigger than anything else. A file that is constantly growing during all other inserts and updates that happen as the project is running will likely become interleaved and fragmented to the nth degree. Without fearing data loss we dropped the credited job indexes and that alone broke the dam. Well, jeez.

We're still catching up from the backlog, but mysql is performing incredibly well at this point. This is good, as we're hoping to release Astropulse before the end of the week. More on that later.

Happy Bastille Day, by the way.

- Matt
Click to expand...

#____Total Work Done____Todays WD_______AWD________overtake________Team-name
01______604.197.775____1.359.998____1.075.742______impossible______SETI.USA
02______436.588.720______673.804______549.719______impossible______SETI.Germany
03______194.160.451______304.164______244.573______impossible______L'Alliance Francophone
04______130.989.492______-77.093______-28.295______4.629 days______BOINC Synergy
05______121.532.182_____-128.609______-46.791______2.597 days______BroadbandReports.com Team Starfire
06______115.478.049______-10.315_______-3.483_____33.155 days______Czech National Team
07______114.437.327______244.330______171.564______impossible______The Knights Who Say Ni!
08______112.764.691_______40.054_______41.625______impossible______SETI@Netherlands
09_______64.342.972________9.510_______98.642______impossible______Overclockers.com
10_______36.652.276_____-195.378_____-142.668________257 days______Team Art Bell
11_______36.340.691______-80.185______-33.630______1.081 days______Team 2ch
12_______32.267.163_____-180.277_____-110.294________293 days______Team MacNN
13_______30.647.340_____-170.655_____-102.655________299 days______OcUK - Overclockers UK
14_______27.281.894_____-116.235______-76.885________355 days______The Planetary Society
15________4.884.647______-64.877________1.114______impossible______Team Starfire World BOINC
16________4.706.129______-82.791______-66.232_________71 days______Team China
17________3.892.547______-65.510______-14.962________260 days______SETI@Taiwan
18______117.970.610______457.800______345.474______notanoption_____TeAm AnandTech
19_______-2.766.754_____-316.212_____-232.960______impossible______BOINC.Italy
20_______-5.139.939_____-277.858_____-212.267______impossible______Ars Technica
21______-13.581.620_____-291.580_____-184.133______impossible______Phoenix Rising
22______-21.507.526_____-322.583_____-240.357______impossible______Universe Examiners
23______-22.451.645_____-161.142_____-130.237______impossible______Canada
24______-25.085.507_____-115.142______-61.546______impossible______US NAVY
25______-30.997.652_____-239.776_____-167.579______impossible______Dutch Power Cows
26______-31.593.220_____-123.559______-61.827______impossible______U.S.Air Force
27______-31.604.916_____-200.533_____-138.390______impossible______UK BOINC Team
28______-32.511.860_____-291.490_____-185.875______impossible______AUSTRIA - NATIONAL - TEAM
29______-33.069.511_____-186.176_____-119.980______impossible______PC Perspective Killer Frogs
30______-33.461.619_____-177.218_____-110.760______impossible______Amateur Radio Operators
31______-37.112.549_____-183.603_____-130.289______impossible______BOINC@AUSTRALIA
32______-40.673.664_____-240.650_____-179.081______impossible______BOINC SETI@home RUSSIA
33______-43.033.363_____-283.117_____-202.368______impossible______Team NIPPON
34______-46.142.278_____-358.772_____-278.225______impossible______Hewlett-Packard
35______-47.370.121_____-308.114_____-211.060______impossible______BOINC@Denmark
36______-48.349.775_____-292.124_____-226.761______impossible______Hungary
37______-49.867.990_____-350.780_____-270.304______impossible______Team MacAddict
38______-54.561.541_____-219.636_____-146.012______impossible______BOINC@Poland
39______-56.060.769_____-298.411_____-221.094______impossible______Planet 3DNow!
40______-59.114.514_____-382.009_____-282.675______impossible______2CPU.com
41______-61.219.594_____-353.668_____-262.205______impossible______SETI@klamm.de
42______-61.666.088_____-376.752_____-270.602______impossible______SETI.hr
43______-61.686.311_____-250.629_____-164.466______impossible______Elite Games
44______-63.250.732_____-346.571_____-262.792______impossible______Portugal@Home
45______-67.328.811_____-372.966_____-272.891______impossible______BOINC.SK
46______-68.223.656_____-360.995_____-271.427______impossible______SETI Sverige [Sweden]
47______-68.444.735_____-340.684_____-259.010______impossible______BOINC.BE
48______-69.719.920_____-361.832_____-278.122______impossible______HispaSeti & BOINC
49______-69.890.053_____-379.400_____-277.108______impossible______Team EDGE
50______-70.612.478_____-409.897_____-312.429______impossible______Boone Community School District - Iowa


Appart for Anandtech's stats, it shows how much more/less than Anandtech.
Also shows based on Average Work Done how many days for Anandtech to overtake the team, or be overtaken by a team behind...


Funny stats due to the various server-problems, and long Validator-backlog finally drained.

 
Astropulse is a distributed computing project that is (will be) searching for primordial black holes, pulsars, and ETI, using the Berkeley Open Infrastructure for Network Computing (BOINC) platform.

Astropulse is a project that takes data from the existing SETI@home tapes and re-examines them for radio pulses that lasted only microseconds. This could indicate a pulsar or maybe a signal from an intelligent source deliberately being sent out.

Work on a new Astropulse will start once the SETI enhanced client is in general release. The Southern hemisphere is another SETI project that is due to join BOINC in the future. SETI@home beta is a test environment for these three future projects.

This is the entire article on WIKI. 🙂
 
Originally posted by: BlackMountainCow
Thx for the stats RD! :beer:

Now, what is Astropulse? New client? New science?
Click to expand...
Astropulse will be a new Application, running alongside the current SETI@home-application. Astropulse is a new way to look for ET-signals, and will compliment the "normal" SETI-Enhanced-application. Since the probability of detecting ET-signals is fairly low, the odds is Astropulse will mainly detect black holes, pulsars and so on, which is basically by-products of the search for ET-signals.

As long as you're not using self-compiled/optimized SETI-application, you'll automatically get Astropulse then needed, and will randomly download both Astropulse-wu's and SETI-multi-beam-wu's.

For optimizers, you'll have to upgrade app_info.xml, if wants to also get Astropulse.

If same setup will be used on release as in beta, Astropulse-wu's will be 8 MB's downloads, take around 2 days on a 2 GHz C2D, and have a month long deadline...


 
You must log in or register to reply here.
Back
Top