D1856: wireproto: server-side support for pullbundles

[joerg.sonnenberger (Joerg Sonnenberger)]

joerg.sonnenberger added a comment.


  For my test case, which is a bundle of all changes in the NetBSD repo before 2014 and a yearly bundle afterwards until 2018/1/1 and normal pull for the rest, find_pullbundle needs less than 0.5s of CPU time in this iteration when it matches.
  After the initial clone and with additional available changes, pull time is:
  
  With pullbundles.manifest: 0.42s
  Without pullbundles.manifest: 0.41s
  
  i.e. the difference is the noise level. Further benchmarks by others would be appreciated.
  
  The biggest remaining question for me is whether we want to introduce a capability for the client to mark that it is willing to do multiple pull rounds.

REPOSITORY
  rHG Mercurial

REVISION DETAIL
  https://phab.mercurial-scm.org/D1856

To: joerg.sonnenberger, #hg-reviewers
Cc: mercurial-devel