From 300473e7ade3bb7bcc7f2d92d82061bfbbd8a0c3 Mon Sep 17 00:00:00 2001
From: Joseph Schorr <joseph.schorr@coreos.com>
Date: Thu, 20 Nov 2014 17:30:57 -0500
Subject: [PATCH] Partial fix for high CPU on build status pages

---
 static/css/quay.css | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/static/css/quay.css b/static/css/quay.css
index ae5913db8..1065fa586 100644
--- a/static/css/quay.css
+++ b/static/css/quay.css
@@ -4875,4 +4875,12 @@ i.slack-icon {
 #startTriggerDialog #runForm .field-title {
   width: 120px;
   padding-right: 10px;
+}
+
+.progress.active .progress-bar {
+  /* Note: There is a bug in Chrome which results in high CPU usage for active progress-bars
+     due to their animation. This enables the GPU for the rendering, which cuts CPU usage in
+      half (although it is still not great)
+   */
+  transform: translateZ(0);
 }
\ No newline at end of file