> For the complete documentation index, see [llms.txt](https://sliu583.gitbook.io/blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sliu583.gitbook.io/blog/specific-work/shivarams-group/group-papers/lists/gpu-lifetimes-on-titan-supercomputer-survival-analysis-and-reliability.md).

# GPU Lifetimes on Titan Supercomputer: Survival Analysis and Reliability

### Introduction - Gray XKY Titan&#x20;

![](/files/-MYkGDEGeTxaGcxeEG1N)

* Swapping: due to the resistor&#x20;

### Data Collection & Preprocessing

![](/files/-MYkHDYSRZNX7afX5og1)

* Off the bus: cpu lose connection to GPU
* double bit error: error detection (in GPU memory)&#x20;

Reboot: software update or hardware swap&#x20;

* Aggregate data associated with that GPU, one row per GPU to show the location and period of time&#x20;

Portion of reboot or entire system? Whole system reboot&#x20;

### Data Cleansing&#x20;

![](/files/-MYkItBqEe2o0WPFL1p3)

### Intuition for GPU Lifetimes&#x20;

![](/files/-MYkJQtKvSeT9rAPOlUl)

* Install time: black dot&#x20;
* Blue square: OTB event&#x20;
* Red triangle: GDB event&#x20;
* Square: last seen event of the GPU&#x20;

2017: failing resistor&#x20;

* Had to do hardware/GPU swap&#x20;
* Installation

New batch: after 17

Old batch: more OTB event&#x20;

![](/files/-MYkJxJqDr6dylyGKtom)

Small gaps during the location, but overarchingly all operations are operational&#x20;

* 4 GPUs per blade&#x20;
  * Take the blade out and replace the GPU on the blade&#x20;
  * Put that blade back in different locations&#x20;
* 1 GPU affected&#x20;
  * Entire blade is removed&#x20;

![](/files/-MYkKFN52DDycLpTqenD)

* Distribution similar&#x20;
* Number of DBE > OTB&#x20;

![](/files/-MYkKv_5-oEbq4IwfoPK)

![](/files/-MYkLFTm33evW84UZAig)

![](/files/-MYkMAt4lhV42TFt3MhZ)

![](/files/-MYkN6fHEAgTBBv56QBI)

* Cage: where the GPU is in&#x20;

![](/files/-MYkOhGLEpS3tgNkzS8b)

Relative values compared to the other cages&#x20;

* Cage 2 higher than Cage 0 and 1 (hazard ratio)&#x20;
* Column level&#x20;
  * Columns were next to service system&#x20;

![](/files/-MYkPSD1Q4rwYqavEO_z)

* Interleaving level from column 0 to 11&#x20;

![](/files/-MYkPWyn6rd3xZoAIHcj)

* Torus: network interconnect at the super computer&#x20;
* Lower column number with lower x coordinate v.s lower column number with high x coordinate has a higher hazard ratio&#x20;
  * Job scheduling impacts the overall performance&#x20;
  * Workload is not balanced&#x20;
    * GPU with lower torus: more workloads&#x20;
    * Why?
      * Cluster is not full (70% of the cluster used)&#x20;
      * Which machine?&#x20;
        * Assign at the beginning with higher probability&#x20;
    * Awareness?&#x20;
* Good outcome: consistently around for 1 is the ideal scenario&#x20;

![](/files/-MYkQ7jqL50xDp829t9O)
