4 ms·

Thanks, I've now read it. Very nice. I guess having your architecture out in the open is liberating in that sense. So now two specific questions: 1. So why did

by dvirsky 12y ago

Thanks, I've now read it. Very nice. I guess having your architecture out in the open is liberating in that sense. So now two specific questions: 1. So why did you have a big read spike? And 2. are you going to share the TODOs as well? :) BTW We're using gitlab internally (at EverythingMe) and are very happy about it, especially the flow of fixes and features implemented.

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 ago
  I 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 ago
  Right 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.