HECToR Monthly Report, April 2009
Information on the utilisation, disk allocations, slowdowns and helpdesk statistics can be found in the associated SAFE monthly report.
Dates covered: 08:00 1 April 2009 to 08:00 1 May 2009
Number of hours: 720
Scheduled down time: 14.5 hours.
The following incidents were recorded:
Of the four severity levels, level 1 corresponds to a contractual failure.
Out of the 27 SEV-3 Incidents, 27 were attributed to single node failures.
Details of severity level 1 incidents
|Incident-1236||03/04/2009||Link Inactive c18-0c1s1s3l1 c16-0c1s1s3l4||02:20||Cray|
|Incident-1276||07/04/2009||Overload of Lustre||02:07||Cray|
MTBF and Serviceability
- Note 1: Serviceability%= 100*(WCT-SDT-UDT)/(WCT-SDT)
- Note 2: MTBF (Mean Time Between Failures) is defined as 732/Number of failures.
Details of XT single node failures
|RX message header CRC Error||11|
|MCA bk0/bk2 error (Internal Opteron)||5|
|UME bk0/bk4 (Dimms)||3|
|Coldstart error (node failing to restart after reboot)||2|
|Kernel panic "tx DMA vector invalid"||1|
Note: During "coldstart" and "admin down" errors, no user jobs were affected.
2: CoursesThis information is supplied by NAG Ltd
|Title of Course||Dates||Available places||Ordinary attendees||Paying attendees||CSE Staff||Total attending|
|Programming the X2 Vector System, NAG Oxford||2 - 3 April 2009||12||5||0||2||7|
|Introduction to High Performance Computing, University of Warwick||20 - 24 April 2009||12||8||2||0||10|
3: Quality tokens
|21-Apr-2009 16:07:48||* * * * *||positive feedback from e42|
|07-Apr-2009 11:40:08|| ||Our research group is begining to suspect your machine status notification system is failing. Hector has been down several times this month without apparent action being taken until we have sent an email to helpdesk, often while web says Hector 'open'.|
4: Hours worked
5: Performance metrics
|Technology throughput||7000 hours||8367 hours||8535 hours|
|Capability job completion rate||70%||90%||100%|
|Technology MTBF||100 hours||126.4 hours||244 hours|
Note: Technology throughput is calculated: 12*(732-UDT-SDT); 732 - annual average number of hours in a month
Note: MTBF is calculated as 732/number of failures
|Percentage of non-in-depth |
queries resolved within one day
|Number of SP FTEs||7.3||8.0||8.7||8.8|