Niluge kiwi <kiwiiii@xxxxxxxxx> wrote: > Hi all, > > In magit (http://magit.github.io/), a popular git frontend within > emacs, there is a git-svn frontend. With a recent refactoring, it was > discovered that git-svn metadata commands (like "git-svn info") are > much slower than git ones: > git svn info: 130-150ms (after warmup): get the svn revision and url. > git svn rebase --dry-run: 150-170ms (after warmup): get the remote > branch. > > Whereas in pure git: > git rev-parse --abbrev-ref HEAD@{upstream}: 2-3ms (after warmup): get > the remote branch > Other git commands alike take all less than 10ms after warmup. Thanks for the bug report. I actually see worse performance from my old machines, but I'm not a very heavy git-svn user anymore. 100ms is an eternity :< > This is an issue for the magit developers and users: just getting a > git-svn status with some metadata easily take ~500ms, which is really > slow for a UI. The equivalent UI with a pure git repository in magit > takes much less than 100ms to generate although more than 30 git > process are forked for it. How big is the parent process which forks the git commands? On Linux at least, fork() performance is negatively impacted by parent process memory size. To avoid spawn performance problems with large parent processes, vfork() should be used, but there does not seem to be an easy/portable way to use vfork() from Perl. > A previous version of magit-svn was much faster because it > re-implemented the logic of git-svn from perl to elisp (the > programming language in emacs), and to get the 3 previously mentioned > values it took less than 10ms. I've never worked with elisp, but we can probably figure out why it's faster. Can you give us a pointer to the old elisp code? > What could be done about this? > Could git-svn performance be dramatically improved? > Even git svn --version takes ~100ms, is perl the bottleneck? The Linux 'perf' tool reports much time is spent is from the Perl parser. So we may implement lazy loading, so simple commands such as "git svn info" do not need to load and parse all the Perl code. > Or should each git-svn frontend developer re-implement the git-svn > metadata commands themselves for better performance? I prefer git-svn be fast enough; but you're free to reimplement and optimize your own code as you see fit. > Also, wouldn't it be better for those frontend developers if there > were some git-svn porcelain commands like git has? Fast, easy to parse > and stable input & output format? Sure, but we don't know what you'd need beyond the current command set. Of course we need to be careful about adding even more code to git-svn as that impacts startup time, too. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html