I'm using GitLab Omnibus (7.7.2 bd98290) on my own local server (a xenserver VM with 8 core Xeon E5-2620 2GHZ, 8GB RAM, SATA RAID1 local disks).
I've created a repository with a clone of linux-stable (git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git), working on branch master (current HEAD 26bc420b59a38e4e6685a73345a0def461136dce) I'm experiencing a performance issue when doing, e.g., a blame on Makefile. It reports a 502 error, by looking at logs it's a 60 seconds timeout (I didn't try with a larger timeout). I also try with plain git command from SSH shell and it takes only a couple of seconds root@gitlab:/var/opt/gitlab/git-data/repositories/a.scian/linux-stable.git# time git blame master -- Makefile > /dev/null real 0m10.337s user 0m4.344s sys 0m0.415s Am I missing something? Did I have something wrong on my GitLab installation? I'm new to GitLab world, but maybe the problem here is all the stuff GitLab adds to the blame view, e.g. icon of committers and so on. WDYT? If so, is it possible to configure a lightweight version of blame in GitLab? I also try nearly the same project in gitlab.com <https://gitlab.com/amonthedeamon/linux-kernel-test/blame/master/Makefile> having the same 502 timeout (it think gitlab.com has the same 60 secs timeout) TIA, Andrea -- 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/91dbd45c-f76e-4993-9e55-8d8f334e391a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
