[MERGE] first round of use case benchmarks

[Carl Friedrich Bolz]

John Arbash Meinel wrote:
[snip]
> The permutations seem reasonable, though.
> I wonder if it would be better to separate the timing. 1 time evaluated
> for generating the bundle, and another time for reading and installing
> the bundle. Though that ends up doubling the number of tests you write.

Hum. I agree in principle, but it seems to just take too long to build
the trees. The test_many_files_big_tree_1000_revision takes a _long_
time on my machine just as it is, so building the tree twice does not
sound like it is a good idea to me.

Maybe we could add smaller separate writing and installing benchmarks?

In general it seems that install_bundle is horribly slow, will profile a
bit.

> ...
>
> v- Seems okay. Ultimately we probably would want to test one of your
> 'make_many_commit_tree()' trees as well.

Yes, but in the next merge request, I would say :-)
>
>> +class InfoBenchmark(Benchmark):
>> +    """This is a stub. Use this benchmark with a network transport.
>> +    Currently "bzr info sftp://..." takes > 4 min"""
>> +
>> +    def test_no_ignored_unknown_kernel_like_tree(self):
>> +        """Info in a kernel sized tree with no ignored or unknowns. """
>> +        self.make_kernel_like_added_tree()
>> +        self.time(self.run_bzr, 'info')
>> +
>> +    def test_no_changes_known_kernel_like_tree(self):
>> +        """Info in a kernel sized tree with no ignored, unknowns, or
added."""
>> +        self.make_kernel_like_committed_tree()
>> +        self.time(self.run_bzr, 'info')
>

[snip]

Attached is an updated version of the patch.

Cheers,

Carl Friedrich
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bench_usecases.patch
Type: text/x-patch
Size: 16935 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060830/c4cc3697/attachment.bin