3 ms·

I can't speak for other browsers, but keeping a GitLab tab open in a background tab consistently causes my CPU dedicate 15-25% of its cycles to Firefox. I do f

I can't speak for other browsers, but keeping a GitLab tab open in a background tab consistently causes my CPU dedicate 15-25% of its cycles to Firefox. I do file bugs against GitLab every now and then, but I haven't done so for this one because I assume that there's an existing item on file for this (and I don't care to look for it) and that this is all part of the the longstanding, "Yeah, we really need to work on our frontend story, especially for mobile." The end result is that just don't keep GitLab tabs open. Which is a little obnoxious, given the well-known issues with how slow GitLab is to complete requests.

sytse 10y ago
Mmm, I found https://gitlab.com/gitlab-org/gitlab-ce/issues/521 https://gitlab.com/gitlab-org/gitlab-ce/issues/521 but that was a Firefox bug. It is probably something in GitLab but I'm not sure someone filed a bug report for it. We have complete UX and frontend teams and at this moment all the views should work great, also on mobile. GitLab self-hosted should be fast but we're working on the speed of GitLab.com.
- godfat 10y ago
  Here's another issue about Firefox using 100% CPU https://gitlab.com/gitlab-org/gitlab-ce/issues/342 https://gitlab.com/gitlab-org/gitlab-ce/issues/342