[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jgit-dev] jgit push on http perpetually running gc before push after jgit gc
performance issues during transports often have to do with specific
attributes of the sending of receiving repo. During push the number of
references which the receiving repo knows of plays a role and also how
on sending side refs and objects are packed. Would of course be nice
if you can really reproduce that effect with a up to date jgit and a
open-source repo but I am not sure how good your chances are. Feel
free to try.
As a parallel task you could share some data about your setup. What
does 'git count objects -v' on sending and receiving repo output just
before a slow push. What does 'GIT_TRACE_PACKET=1 git push ...' on
command line return. Always be careful that actions you do with native
git doesn't automatically repair the situation and double check that
the next jgit push is still slow.
On Thu, Mar 14, 2019 at 9:42 AM Thibault Kruse <tkruse@xxxxxxxxxx> wrote:
> no, we cannot share the code or the repository. But if we invest time, we feel confident that we could create a shareable example, because the code we use to reproduce only uses jgit. And we feel confident we could use some publicly available large repo from github to reproduce.
> We did not turn autogc on explicitly, so we assume it runs as default during git push with default parameters. With jgit3x it seems to be triggered after 12h, with jgit5x it seems to be triggered after several hours. If we knew what triggers autogc, that would help us a bit in fixing.
> On Thu, Mar 14, 2019 at 5:32 PM Christian Halstrick <christian.halstrick@xxxxxxxxx> wrote:
>> Hi,sounds very interesting especially because it seems so
>> reproduceable. I guess you can't share the repository?
>> Which parameters do you use to run the gc. Do you have autogc turned on?