Some unscientific timing results (on the Python source tree)
Ville M. Vainio
vivainio at gmail.com
Mon Mar 24 14:18:27 GMT 2008
On Mon, Mar 24, 2008 at 2:16 PM, Paul Moore <p.f.moore at gmail.com> wrote:
> relevant in making a choice. As I said, I am personally very close to
> a point where I would choose (and advocate) Mercurial over Bazaar for
> any significantly-sized project, based on the speed difference. And if
> the Bazaar team don't feel a need to improve speed further with "as
> fast as other DVCSs" as a target, then that pushes me even closer to
> deciding on Mercurial.
This makes me think - would it make sense to make some unorthodox
optimizations? I'm speaking of creating a temporary cache for data
that is currently slow to compute? I.e. something that *is* derived
information and would never need to be transferred around, but would
help local performance. Perhaps a "bzr optimize" command...
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'
More information about the bazaar