On Jun 11, 2020, at 11:33 PM, Greg A. Woods <woods%planix.ca@localhost> wrote:
I then did: "hg init src && cd src && hg unbundle $bundle"
The unbundle finally finished the first step (unpacking all 931,876
changesets) after about 15 minutes and began on the manifests, just as
with the clone operation did.
The manifests then completed, unlike the attempts via the network,
though I don't know how long that took, and now it's checking out
439,702 "file changes", saying it will be taking over 2hrs to complete.
HG has the world's second-worst task time estimator though -- it's been
waffling between 10 to 30 mins for the past hour or more (on the "files"
step).
Overall that's _STUNNINGLY SLOW_ compared to a "git clone" of the same
NetBSD source tree -- especially since I've eliminated the network for
the HG test case!
How much RAM do you have in that machine? Could some of that time waffling be due to the system thrashing to swap? My experience with doing similar tests is hg required >3GB of RAM+swap to complete, and Git required about one-quarter the memory.
jf
|