Rosetta@home

Server Status Page

  UW Seal
 
[ Home ] [ Join ] [ About ] [ Participants ] [ Community ] [ Statistics ]
  [ login/out ]

As of 9 Feb 2010 16:29:19 UTC   (updated every 10 minutes)

Server status

ProgramHostStatus
Data-driven web pagesboinc.bakerlab.orgRunning
Schedulersrv4.bakerlab.orgRunning
rah_make_work1srv1Running
rah_make_work2srv3Running
feedersrv4Running
file_deletersrv1Running
rah_validator_betabk2Running
rah_validator_minibk1Running
rah_assimilatorbeta1bk1Running
rah_assimilatorbeta2bk1Running
rah_assimilator_mini1bk1Running
rah_assimilator_mini2bk1Running
rah_assimilatorbeta3bk2Running
rah_assimilatorbeta4bk2Running
rah_assimilator_mini3bk2Running
rah_assimilator_mini4bk2Running
transitionerboincRunning
db_purgesrv1Running
Running:Program is operating normally
Not Running:Program failed or ran out of work
Disabled:Program has been disabled by staff
(for debugging/maintenance)
   

Database status

StateApproximate #results
Ready to send29,274
In progress503,820


Rosetta@home Hardware

Web servers: boinc, srv1, srv2, srv3, srv4
  • Web servers: boinc, srv1, srv2, srv3, srv4
    • dual 2.4 GHz Xeon (w/ hyperthreading)
    • 2 GB RAM
    • 2.6.9-34.EL SMP kernel (32 bit)
    • dual GB NIC
  • Database server
    • Dell 2950, dual-quad 2GB Xeon E5405 w/ 6MB cache
    • 32 GB RAM
    • mirrored root raid, running 2.6.18-92.1.22.el5 (64 bit)
    • the database files are written to a hardware mirror of two 15K 300GB disks
    • dual GB NIC
  • Fiber SAN fileserver
    • two Dell 2950's
    • clustered fileserver running Polyserve's Matrix Server
    • 16 450 GB SATA disks as a single RAID5 LUN
    • 2GB redundent fiber network
     

Glossary

Programs

  • Data-driven web pages: Public web pages that require database access to be generated. Pages like the forums, or ones that contain statistics or client version information, etc. are occasionally turned off (by hand) when the database is down.
  • Make_work: Generates new work units.
  • Scheduler: Determines what work is going to be sent to/received from requesting clients. If this is off, you cannot send any results or receive any workunits.
  • Feeder: Fills up the scheduler work queue with workunits ready to be sent. The scheduler is too busy handling transaction with clients so the feeder does this job.
  • File_deleter: Deletes input/output files when no longer needed. This program keeps our upload/download disks as clean as possible.
  • Transitioner: Handles state transitions of workunits and results. Basically, the transitioners keep track of the many, many results in progress and makes sure they properly move down the pipeline. It is always asking the questions: Is this workunit ready to send out? Has this result been received yet? Is this a valid result? Can we delete it now?
  • Validator: Validates Rosetta@home work returned by the clients, checkes the data integrity and then issues credit to responsible users accordingly.
  • Assimilator: Takes scientific data from validated results and puts them in the Rosetta@home master database for later analysis.

Home | Join | About | Participants | Community | Statistics

Copyright © 2010 University of Washington

Last Modified: 5 Jan 2010 0:40:29 UTC
Back to top ^