Problems with new streaming API
John Arbash Meinel
john at arbash-meinel.com
Wed Jan 16 22:35:46 GMT 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just got a new laptop, so I'm setting it up with all new bzr
repositories, etc. I did a "bzr checkout bzr+ssh:///" over the local
network to get the latest bzr.dev snapshot.
I thought it would be fast, but I found out a few things.
1) With a client of 1.0.0, it uses the old stream api, which causes the
server to spend a lot of time thinking, and buffering up 240MB in RAM. I
don't really understand why it is so much, considering my repository is
only 85 MB total.
But anyway, because of that buffering time, the network is empty, and at
the end of it shoves a bunch of data and finishes
bzr checkout 21.43s user 1.23s system 11% cpu 3:23.30 total
(notice it takes 3min to get the data, but we only spend 21s processing
it on the local end)
2) Since I saw Andrews patches had finally landed, I thought it would be
good to test them out. So far, memory consumption has stayed low (~30MB)
which is good. However, I have almost 0 network traffic, and it has been
15 minutes.
I did an strace on the server side and I basically see it doing this:
mmap2(NULL, 737280, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7601000
munmap(0xb76b5000, 737280) = 0
futex(0x81f0890, FUTEX_WAKE, 1) = 0
It is basically spinning very fast doing that over and over and over
again. (The only thing that seems to change is the address, the "737280"
stays fixed.)
Can you attach to a running python interpreter with pdb?
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHjobCJdeBCYSNAAMRAh+OAKCXErHKNOVFbG8vA6FahGuPbZTjywCfWcx1
lbH0BpIAhq4dvGiXZT2KeI8=
=Hgpe
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list