Comments on: bzr-2.4 faster large tree handling http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/ News, announcements and comments from the developers of the Bazaar distributed version control system Tue, 30 Aug 2011 02:22:57 +0000 hourly 1 http://wordpress.com/ By: » Teaching Version Control @ badocelot's gloomy coffin http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-270 Fri, 24 Jun 2011 05:12:26 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-270 [...] and comes with a fairly straightforward GUI.  Unfortunately, it’s also the slowest (though 2.4 improves this by quite a bit), the least popular, and the most bug-prone (100% more internal errors than either [...]

]]> By: John http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-246 Thu, 19 May 2011 19:17:43 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-246 After another day dealing with handling edge-cases in the update-by-delta code, I’m happy to say it has officially landed as bzr.dev rev 5900.

The current daily ppa shows: 2.4.0~bzr5894~ppa3932.3931~natty1 from 18 hours ago. So I have a strong hope that in 6 more hours we will build at least ~bzr5900 and you’ll be able to get your updated goodness sometime early tomorrow (depending on what Tomorrow is in your local timezone)

]]> By: Christian Reis http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-244 Wed, 18 May 2011 19:55:10 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-244 Well, actually, the Linaro gcc branch is both completely public and guaranteed to contain no added chemicals or embargoed content. Linaro doesn’t actually do any vendor-specific GCC work; it’s only enablement work done within the landing teams, and that usually focuses on the kernel and hardware-dependent middleware.

The gcc-linaro trees are available from https://code.launchpad.net/gcc-linaro

]]> By: SquareCows.com » OpenStack @ Ubuntu Developer Summit http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-243 Wed, 18 May 2011 17:28:53 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-243 [...] They have great improvements and features coming up, including finer-grained bugmail and dramatic speed improvements in bzr handling of large [...]

]]> By: OpenStack @ Ubuntu Developer Summit « Seeing the fnords http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-242 Wed, 18 May 2011 12:54:08 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-242 [...] They have great improvements and features coming up, including finer-grained bugmail and dramatic speed improvements in bzr handling of large [...]

]]> By: Martin Pool http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-241 Wed, 18 May 2011 10:25:32 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-241 I’m pretty sure gcc-linaro is public; it’s just some particular hardware support projects that are embargoed.

]]> By: John http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-240 Wed, 18 May 2011 08:11:49 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-240 No, its the real gcc-linaro tree. I just wasn’t making public about a private branch.

]]> By: Martin Pool http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-239 Wed, 18 May 2011 08:10:25 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-239 I think John’s “70k file tree” is a synthetic tree similar in size to gcc-linaro. It would be good to retry it there.

]]> By: Michael Hudson-Doyle http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-238 Wed, 18 May 2011 07:51:17 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-238 I bet it was the linaro-gcc tree. But yes, it would be nice to include this in the post :)

]]> By: Elliot Murphy http://bazaarvcs.wordpress.com/2011/05/17/faster-large-tree-handling/#comment-236 Tue, 17 May 2011 20:31:23 +0000 http://bazaarvcs.wordpress.com/?p=250#comment-236 This is great work! What data set/source tree did you use for the first set of timings? How do these timings compare against git for the same tree?

]]>