• 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 stats for 15.01.2008.

Rattledagger

Elite Member
Feature Rich (Jan 14 2008)

Things ran quite well over the weekend. Looks like we added the right index to the mysql database to reduce the slow "validator fix" queries. A note about general BOINC/mysql implementation/design: there are a lot of features in BOINC that are seemingly excessive from a single-project perspetive, but are there as every project has different needs. Project-specific factors (server power, workunit processing times, number of active users, min quorum, etc.) make some features less helpful. In the case of "resend lost workunits" (see last thread) this feature, implemented mostly for the benefit of Einstein@home, was most definitely weighing down our database server. We turned this off and have been running smoothly since. There were assumptions this would lead to greater problems down the line (fearing many results will be sitting on disk longer waiting for their redundant pairing to return) but in fact our "results returned and waiting for validation" number has been stable (if not slowly decreasing) since I made the change. Nevertheless, at some point soon we will see if we could optimize/reimplement this code, and Eric is actually making adjustments to the splitter which will perhaps create less "fast runners."

Our new-hardware-to-obtain priorities are shifting. Namely, we need a router (we're not ignoring discussion about this on other threads but we are limited to what we can use for various configuration/policy reasons). We also need a new KVM - our current one in the closet is maxed out and we'd like to get more stuff in the there ASAP. We also need three new desktop systems. Dan's using an old, sloooow solaris system which is out of support. Bob is on a slightly faster solaris system, but needs a safe mysql test sandbox. Josh's old super-cheap windows/intel box is basically a glorified console server.

Had some minor issues due to the root drive on bruno filling up on Sunday. I scanned the drive and found only 4GB of stuff, while "df" was showing 40GB. Eric eventually found a deleted-yet-open file - an infinitely growing httpd log. Apparently httpd log rotation broke at some point, but we cleaned this up. Annoying, but harmless.

Due to increased load in general, I changed the server db stats to update every hour (instead of half hour). Actually it's becoming clearer as we increase active user load and I'm populating credited_job, etc. that the mysql database might be our bottleneck du jour any jour now. There were also some issues with the user-of-the-day selection process which I tracked down and fixed this morning.

- Matt

#____Total Work Done____Todays WD_______AWD________overtake________Team-name
01______398.225.961______740.209______642.596______impossible______SETI.USA
02______330.794.622______871.544______750.658______impossible______SETI.Germany
03______138.164.444______220.253______201.610______impossible______L'Alliance Francophone
04______116.069.044_______39.077_______52.379______impossible______BroadbandReports.com Team Starfire
05______115.179.913______149.243______155.216______impossible______BOINC Synergy
06_______98.258.382_______98.562_______78.288______impossible______Czech National Team
07_______92.299.139______145.475______118.412______impossible______SETI@Netherlands
08_______82.214.784______136.663______134.228______impossible______The Knights Who Say Ni!
09_______43.756.907_______84.207_______67.414______impossible______Overclockers.com
10_______40.653.324_______35.979_______39.364______impossible______Team Art Bell
11_______40.111.132______-46.865______-46.010________872 days______OcUK - Overclockers UK
12_______33.869.000_______48.494_______23.242______impossible______Team 2ch
13_______29.078.320_______21.289_______17.099______impossible______The Planetary Society
14_______28.968.909_______47.693_______40.577______impossible______Team MacNN
15_______22.383.070______-84.813______-84.086________266 days______BOINC.Italy
16_______12.235.267______-21.900______-35.684________343 days______Ars Technica
17________1.292.508_______79.202_______66.432______impossible______Team China
18__________316.131_______41.946_______22.835______impossible______SETI@Taiwan
19_______75.664.426______157.528______154.292______notanoption_____TeAm AnandTech
20_______-1.650.236______-37.531______-41.397______impossible______Universe Examiners
21_______-2.462.788_______-6.660______-20.411______impossible______Phoenix Rising
22_______-2.738.551_______77.694_______69.817_________39 days______Team Starfire World BOINC
23______-14.590.484______-10.153______-17.906______impossible______Canada
24______-15.475.631______-28.721______-40.128______impossible______Dutch Power Cows
25______-17.419.692______-46.146______-50.807______impossible______Amateur Radio Operators
26______-18.036.238______-68.842______-69.180______impossible______PC Perspective Killer Frogs
27______-18.522.390______-93.793______-91.791______impossible______Hewlett-Packard
28______-21.187.743__________638______-12.738______impossible______UK BOINC Team
29______-23.354.523_______41.321_______29.005________805 days______AUSTRIA - NATIONAL - TEAM
30______-23.711.949_______-1.882_______-9.128______impossible______US NAVY
31______-23.927.558______-48.376______-51.896______impossible______Team NIPPON
32______-24.455.839______-66.595______-70.764______impossible______Team MacAddict
33______-24.598.220______-19.745______-42.087______impossible______BOINC SETI@home RUSSIA
34______-24.944.091______-26.793______-34.647______impossible______BOINC@AUSTRALIA
35______-26.379.353______-53.990______-52.059______impossible______BOINC@Denmark
36______-27.018.183______-52.716______-60.469______impossible______Hungary
37______-27.479.109_______-9.517______-20.110______impossible______U.S.Air Force
38______-27.887.010______-97.274______-99.949______impossible______2CPU.com
39______-28.829.241_____-129.352_____-119.661______impossible______Planet 3DNow!
40______-33.711.281______-96.698______-99.803______impossible______Portugal@Home
41______-34.813.383______-73.968______-80.065______impossible______SETI.hr
42______-35.375.933______-69.860______-73.959______impossible______SETI@klamm.de
43______-39.295.081_____-107.343_____-106.220______impossible______Team EDGE
44______-39.308.602______-99.849______-99.743______impossible______HispaSeti & BOINC
45______-39.504.764______-86.555______-91.801______impossible______BOINC.SK
46______-40.294.861______-79.766______-85.836______impossible______SETI Sverige [Sweden]
47______-40.510.956_____-132.435_____-131.171______impossible______Picard
48______-41.398.262______-35.663______-44.468______impossible______BOINC@Poland
49______-41.459.207_____-138.533_____-136.137______impossible______LittleWhiteDog
50______-44.030.209______-99.476_____-102.200______impossible______BOINC UK

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...


 
Back
Top