pcarranza

6 ms·

1.
by pcarranza 10y ago
Thanks mtanski, this is great data. We are running a recent kernel as in ubuntu 16.04. The reason I'm framing the caching not so much at the CephFS level is because we are shipping a product, and I don't think that all our custome
2.
by pcarranza 10y ago
You are right regarding many small files. Interestingly reading from many small files didn't seem to be so much of a problem with CephFS as it was to keep a large file open while reading and writing to it from thousands of processes (t
3.
by pcarranza 10y ago
It's not updates, it's just querying, updates are not that bad, the main issue there was that the CI runner was keeping a lock in the database while going for the filesystem to get the commit, this generated a lot of contention. S
4.
by pcarranza 10y ago
Infrastructure issues are here: https://gitlab.com/gitlab-com/infrastructure The one about the load balancer is https://gitlab.com/gitlab-com/infrastructure/issues/467 but we don't
5.
by pcarranza 10y ago
The original document is here, it is publicly visible: https://docs.google.com/presentation/d/1qxezL1lSn9SyLGMZRXFU... Regarding web performance, these last days we had really good progress: https://git
6.
by pcarranza 10y ago
The main issue with this is that this would be a vendor specific solution that would lock everybody. We build a product that you can host yourself. If we only solve the scaling issue by pushing it down to a specific vendor, then there is no
7.
by pcarranza 10y ago
Hi dineshp, I'm Pablo Carranza, and I am currently leading the effort on infrastructure at GitLab, this includes performance. > what are the major areas where you face performance issues? > Does the choice of RoR play a part in p