Speedup with history-db
Eli Zaretskii
eliz at gnu.org
Fri May 27 15:09:59 UTC 2011
> Date: Fri, 27 May 2011 16:49:35 +0200
> From: John Arbash Meinel <john at arbash-meinel.com>
> CC: bazaar at lists.canonical.com
>
> > 13.578 history_db post-change-hook took 1.638s (0.012s to get_config, 1.526s to init, 0.100s to import)
> > 13.578 Stats:
> > {'num_search_tips': 0,
> > 'step mainline': 1,
> > 'step mainline added': 4,
> > 'step mainline cache missed': 1,
> > 'step mainline initial': 1}
> > [ 4216] 2011-05-27 17:06:14.640 INFO: Tree is up to date at revision 104384 of branch bzr+ssh://eliz@bzr.savannah.gnu.org/emacs/trunk
> >
> > What is it trying to do for 1.6s?
>
> If you have a branch that has not been imported before, bzr-history-db
> is importing it into the db now.
There's no branch that wasn't imported before.
> Note that it did find 4 revisions that were not present in the
> ancestry.
Is there any way to find out the revision IDs of those revisions? I'd
like to see what they are.
> Counting the whole revision table is stupid. I just committed what
> should be a fix for that (revno 135).
Thanks. This slashed the time significantly, but bzr consistently
says it imports 4 revisions each time I do a "bzr up" with no new
revisions available in the remote repo:
9.360 fetch up to rev {rgm at gnu.org-20110527071815-pnm36i0e38mb8wte}
11.766 history_db post-change-hook took 0.246s (0.002s to get_config, 0.096s to init, 0.148s to import)
11.766 Stats:
{'num_search_tips': 0,
'step mainline': 1,
'step mainline added': 4,
'step mainline cache missed': 1,
'step mainline initial': 1}
[ 3688] 2011-05-27 18:06:55.062 INFO: Tree is up to date at revision 104384 of branch bzr+ssh://eliz@bzr.savannah.gnu.org/emacs/trunk
It looks like something else is at work here.
More information about the bazaar
mailing list