We are seeing the same issue with the blame button in Gitlab. Clicking the blame button for files with a long history is very slow. The slow response is apparent on our local installation so we cloned the repository on gitlab.com and we are seeing the same problem. For example, on gitlab.com:
https://gitlab.com/jake-stookey/kw-gh-test/blame/master/CMake/CTestCustom.cmake.in Blame takes about a minute to complete during which time a ruby process on the server runs at 100% CPU usage, sometimes timing out after a minute with a 502 response ("GitLab is not responding"). If several of these request are running at once, the server can become unresponsive to other requests. The blame operation on the same file on github is nearly instantaneous: https://github.com/Kitware/VTK/blame/master/CMake/CTestCustom.cmake.in Similarly, generating a blame report using a checked out copy of the repository from the command line (/usr/lib/git-core/git-blame CTestCustom.cmake.in) on our gitlab server completes in less than a second. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/47cab118-3bff-4464-aad8-c86120cb11c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
