Chances are good that most of the time is spent in Git commands. You could probably get a good approximation of what's taking long by looking at which git commands are running and for how long.
On Thu, Jul 8, 2010 at 2:48 PM, Ævar Arnfjörð Bjarmason <[email protected]>wrote: > I don't have any experience profiling elisp libs in general, so bear > with me. > > I find that Magit is very slow when working on big Git projects M-x > magit-status on git.git (the repo for Git itself) can take up to 10 > seconds on my slow laptop, running the equivalent git commands to get > a list of stashes, running git status etc. would take an order of > magnitute less. > > Staging individual hunks can be very slow, much slower than using git > add --interactive manually. > > I don't have these performance issues on smaller repositories, but > even there I find magit much slower than running the equivalent Git > commands, some common tasks take 100-200 ms. While equivalent Git > commands might take ~50 ms at most. > > Is there anything I can turn on to profile magit to see what the slow > parts are? I suspect that it might be parsing a lot of output slowly > in Elisp that it doesn't need. >
