lightweight checkout over hpss is slow, many roundtrips
Bug #762330 reported by
Martin Pool
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Jelmer Vernooij |
Bug Description
'bzr checkout bzr+ssh:
427.952 Transferred: 140628kB (328.7kB/s r:140607kB w:21kB)
427.952 return code 0
[13818] 2011-04-16 10:08:26.471 INFO: HPSS calls: 113 (103 vfs) SmartSSHClientM
the final tree is 88MB.
Related branches
lp:~jelmer/bzr/hpss-iter-files-bytes
- Martin Pool: Approve
-
Diff: 566 lines (+259/-43)12 files modifiedbzrlib/remote.py (+90/-20)
bzrlib/revisiontree.py (+5/-4)
bzrlib/smart/repository.py (+65/-6)
bzrlib/smart/request.py (+5/-0)
bzrlib/tests/blackbox/test_cat.py (+1/-1)
bzrlib/tests/blackbox/test_export.py (+1/-1)
bzrlib/tests/per_bzrdir/test_bzrdir.py (+6/-2)
bzrlib/tests/per_repository_vf/test_check_reconcile.py (+2/-1)
bzrlib/tests/test_remote.py (+45/-6)
bzrlib/tests/test_smart.py (+33/-1)
bzrlib/vf_repository.py (+1/-1)
doc/en/release-notes/bzr-2.5.txt (+5/-0)
Changed in bzr: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
status: | Confirmed → In Progress |
milestone: | none → 2.5b4 |
Changed in bzr: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Likewise, 'bzr checkout --lightweight lp:gcc' downloads almost 8GB of data while project data is less than 1GB (metadata excluded, since it's lightweight).
On the mailing list I got told that lightweight checkouts are not intended for network use, but for local checkouts. In that case light checkouts should be disabled for network protocols, or at least show a big fat warning to the user. It is *very* discomforting for someone to try "lightweight" checkout to be faster than heavy operations, only to wait 5h-6h without progress percentage being displayed to have a clue that it won't finish anytime soon.
I know now that lightweight checkouts are not intended for use over network, but my first impression was that it meant downloading only data, no metadata at all, with all logic being computed server side. I was actually expecting it to be as lightweight as wget...