Timeout issues - Gitlab error page
Created by: danielkummer
We've started using the Gitlab server in production and are experiencing timeout issues with more users using it... The result is always the "Gitolite Error Page". I think a good way to go about it is retrying failed gitolite operations more times before presenting an error screen for the failed operation. If there's some potential for improval of the whole gitolite handling it would also work towards solving the problem...
Question: Why isn't the gitolite-admin repository clone kept and only updated before changing the configuration? It seems to me gitlabhq always clones a fresh copy of the admin repository just to (for example) add a new user or repository.