It looks like git's blame has optimizations that libgit2's blame lacks:
https://github.com/libgit2/libgit2/issues/3027
Jake
On Tuesday, March 31, 2015 at 5:04:35 PM UTC-4, jstookey wrote:
>
> The delay is apparent using the rugged library with a standalone ruby
> script on a local repository ch
The delay is apparent using the rugged library with a standalone ruby
script on a local repository checkout.
== test.rb ruby script ==
require 'rugged'
@repo = Rugged::Repository.new('/home/jake/tmp/vtk')
@blame = Rugged::Blame.new(@repo, 'CMake/CTestCustom.cmake.in' )
@repo.close
== command tak
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:
h
Il giorno venerdì 20 febbraio 2015 11:40:29 UTC+1, Andrea Scian ha scritto:
>
>
> 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 just read the news t
Hi Sytse,
Il giorno martedì 3 marzo 2015 02:31:24 UTC+1, sytse ha scritto:
>
> Hi Andrea,
>
> It would be better to render the page and get the information via one
> or more ajax requests, this way the page doesn't time out.
>
This sounds good to me but also sounds as a deeper changes inside
Hi Andrea,
It would be better to render the page and get the information via one
or more ajax requests, this way the page doesn't time out.
Best regards,
Sytse Sijbrandij
CEO GitLab B.V.
On Mon, Mar 2, 2015 at 3:37 PM, Andrea Scian wrote:
>
> Sytse,
>
> I don't really know if the issue is the
Sytse,
I don't really know if the issue is the same, because I'm pretty new to
gitlab and its internals (but I have a few year of experience in managing
"big" git repository from command line)
I was wondering if there's a way to "simplify" gitlab blame view. Let's
say: if the call timed out a
This issue (or a similar one) is being discussed in
https://gitlab.com/gitlab-org/gitlab-ce/issues/859#note_889474
Best regards,
Sytse Sijbrandij
CEO GitLab B.V.
On Fri, Feb 20, 2015 at 2:40 AM, Andrea Scian wrote:
>
> I'm using GitLab Omnibus (7.7.2 bd98290) on my own local server (a xenserver
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 ma
