Óscar Fuentes writes:

> Christopher Allan Webber
> <[email protected]> writes:
>
>> But I found that as my project grew, magit-wazzup failed to scale for
>> me:
>>  - It was too slow.  My project had about 500 or so branches and
>>    magit-wazzup would check *all* of them if they had new commits and
>>    format them all for display.  magit-wazzup had an interface to mark
>>    something as "ignored" but it didn't really work for me because the
>>    branches that should have been ignored didn't show up for me to
>>    ignore them anyway!
>
> Tried with a large repo (Emacs). After invoking magit-review Emacs
> freezes while git/magit-review inspects the repo. After several minutes,
> I canceled the operation by pressing C-g. This is the same problem
> wazzup has, which is unusable on this type of repos.
>
> Does magit-review provide a method for improving this?

I've found that magit-review helps for MediaGoblin, where things are
slowed down drastically by having a ton of branches to review (I have
around 500ish) but that's not accounting for slowness based on history
length itself.

I wonder if you've done "git gc --agressive" if that impacts
performance?  Anyway, it's still using the *general* trick that
git-wazzup is, which does involve trying to find a common head.  What
magit-review does differently is that you're able to move branches over
to a state where you don't see them anymore, such as the ignore
branches, or a subset of branches to focus on, such as the tracking
ones.  But other than that, I don't suspect it has anything else that
helps.

(There is one way where it may be able to become faster in this regard:
it may be able to cache data on which branches have new commits and a
common head, but of course the next time you run a git pull on master
this info won't be useful anymore...)

 - Chris

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"magit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to