8 ms·
1. We don't know (and the read spike might be an effect rather than the cause) 2. Yes, most of the things after the hashrockets (=>) currently in the doc are T
by sytse 12y ago
1. We don't know (and the read spike might be an effect rather than the cause)
2. Yes, most of the things after the hashrockets (=>) currently in the doc are TODO's
BTW Awesome to hear that you are happy users of GitLab.
- dvirsky 12y agoI bet it's an effect rather than a cause. We had some server incident recently that started with a huge write spike on some machines. Turned out it was the nginx error log and the problem itself was something else.
- sytse 12y agoRight now it looks like 1 was caused by an extremely large repo (18 GB) being pushed. Only 0.1% of repos are bigger than 1GB. We're still investigating.