|
Spinhenge@home server status as of 2:15 AM CET on Saturday, 4 February 2012 (updated every 60 minutes).
The Spinhenge@home main server has been continuously up for 242 days 17 hours 15 minutes.
Server status
| Program | Host | Status |
| Spinhenge web server | majestix-1 | Running |
| upload/download server | majestix-1 | Running |
| scheduler | majestix-1 | Running |
| feeder | majestix-1 | Running |
| transitioner | majestix-1 | Running |
| transitioner1 | majestix-1 | Running |
| file_deleter | majestix-1 | Running |
| sample_trivial_validator | majestix-1 | Running |
| sample_trivial_validator1 | majestix-1 | Running |
| spin_assimilator_new | majestix-1 | Running |
| db_purge | majestix-1 | Running |
| sample_trivial_validator_beta | majestix-1 | Disabled |
| spin_assimilator_new_beta | majestix-1 | Disabled |
| sample_trivial_validator_qmc_beta | majestix-1 | Disabled |
| qmc_assimilator_beta | majestix-1 | Disabled |
| Running: |
Program is operating normally |
| Not Running: |
Program failed or ran out of work
(or the project is down) |
| Disabled: |
Program has been disabled by staff
(for debugging/maintenance/not needed) |
|
|
Users and Computers
| USERS | Approximate # |
| in database |
80,952 |
| with credit |
58,706 |
| registered in past 24 hours |
6 |
| HOST COMPUTERS |
Approximate # |
| in database |
213,257 |
| registered in past 24 hours |
33 |
| with credit |
153,142 |
| active in past 7 days |
3,237 |
| floating point speed over all in TFLOPS1 |
387 |
| floating point speed in past 7 days in TFLOPS2 |
8 |
|
|
Database/file status
| State | # |
| Results ready to send |
0 |
| Results in progress |
0 |
| Workunits waiting for validation |
0 |
| Workunits waiting for assimilation |
0 |
| Workunits waiting for deletion |
0 |
| Results waiting for deletion |
0 |
| Transitioner backlog (hours) |
0 |
|
|
1) the sum of the benchmarked FLops/s of all hosts in the database
2) the sum of the benchmarked FLops/s of all hosts that have contacted the Spinhenge@home scheduler within the past week
Glossary
Programs:
- Spinhenge Web server: 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.
- upload/download server: Handles workunit/result transactions initiated by BOINC clients.
When a client requests a workunit, this server sends it out. When a client has
a result to send back, this server reads it and saves it to disk for later validation/assimilation/etc.
- scheduler: Determines what work is going to be sent to/received from requesting clients.
Clients go to the scheduler first to request work, and the scheduler tells the client what to get
and where to get it. If this is off, you cannot get any new work. After a client sends a result
back, it then contacts the scheduler which then marks it as received.
- feeder: Fills up the scheduler work queue with workunits ready to be sent.
The scheduler is usually too busy handling client transactions to maintain such a queue itself.
- transitioner: Handles state transitions of workunits and results.
Basically, the transitioners keep track of the 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?
- Spinhenge Validator: Validates Spinhenge@home results by comparing them with similar
results returned by other users. If enough results for the same workunit have
been returned, the validator compares the data, deems one result from the set the
"canonical" result, and issues credit to all responsible users accordingly.
- Spinhenge Assimilator: Takes scientific data from validated results and
puts them in the Spinhenge@home master database for later analysis.
- file_deleter: Deletes input/output files when no longer needed (i.e. after assimilation).
This program keeps our upload/download disks as empty as possible.
Database/file status states
- Results ready to send (unsent): For each workunit, three "empty" results are generated
that are then sent out to individual users to be filled with data.
This is the number of empty results ready to be sent out.
- Results in progress: Number of results that haven't been returned by their
clients, or are waiting for "quorum" to be reached so validation could take place.
- Workunits/Results waiting for deletion: The number of workunits or results
which can be deleted from disk, as the workunit has been assimilated, and there is no
more use for it or its constituent results.
Server Hardware Infos
Spinhenge Server
|
