Mercurial Workflow: Feature seperation via named branches

[Benjamin Fritz]

2011/6/15  <mercurial-request at selenic.com>:
> Also, I think you underestimate how badly things can go algorithmically
> for people who are not aware that particular things aren't designed to
> scale. For instance, we've had people who've tagged essentially every
> commit in a 100k cset repo. That's simply not going to work well and
> we're not going to be able to tweak things so it does.
>

I'm curious about what problems might arise from tagging nearly every
commit. For instance, Vim is maintained in Mercurial at
http://code.google.com/p/vim , and each new patch added is tagged with
the patch number. What specific problems might occur from this
practice?