upstream/mercurial-mirror Files · mercurial/help/urls.txt

exchangev2: fetch file revisions...

exchangev2: fetch file revisions Now that the server has an API for fetching file data, we can call into it to fetch file revisions. The implementation is relatively straightforward: we examine the manifests that we fetched and find all new file revisions referenced by them. We build up a mapping from file path to file nodes to manifest node. (The mapping to first manifest node allows us to map back to first changelog node/revision, which is used for the linkrev.) Once that map is built up, we iterate over it in a deterministic manner and fetch and store file data. The code is very similar to manifest fetching. So similar that we could probably extract the common bits into a generic function. With file data retrieval implemented, `hg clone` and `hg pull` are effectively feature complete, at least as far as the completeness of data transfer for essential repository data (changesets, manifests, files, phases, and bookmarks). We're still missing support for obsolescence markers, the hgtags fnodes cache, and the branchmap cache. But these are non-essential for the moment (and will be implemented later). This is a good point to assess the state of exchangev2 in terms of performance. I ran a local `hg clone` for the mozilla-unified repository using both version 1 and version 2 of the wire protocols and exchange methods. This is effectively comparing the performance of the wire protocol overhead and "getbundle" versus domain-specific commands. Wire protocol version 2 doesn't have compression implemented yet. So I tested version 1 with `server.compressionengines=none` to remove compression overhead from the equation. server before: user 220.420+0.000 sys 14.420+0.000 after: user 321.980+0.000 sys 18.990+0.000 client before: real 561.650 secs (user 497.670+0.000 sys 28.160+0.000) after: real 1226.260 secs (user 944.240+0.000 sys 354.150+0.000) We have substantial regressions on both client and server. This is obviously not desirable. I'm aware of some reasons: * Lack of hgtagsfnodes transfer (contributes significant CPU to client). * Lack of branch cache transfer (contributes significant CPU to client). * Little to no profiling / optimization performed on wire protocol version 2 code. * There appears to be a memory leak on the client and that is likely causing swapping on my machine. * Using multiple threads on the client may be counter-productive because Python. * We're not compressing on the server. * We're tracking file nodes on the client via manifest diffing rather than using linkrev shortcuts on the server. I'm pretty confident that most of these issues are addressable. But even if we can't get wire protocol version 2 on performance parity with "getbundle," I still think it is important to have the set of low level data-specific retrieval commands that we have implemented so far. This is because the existence of such commands allows flexibility in how clients access server data. Differential Revision: https://phab.mercurial-scm.org/D4491

Josef 'Jeff' Sipek - - Load All Authors

File last commit:

r36372:5da7b8cb stable


                r39676:039bf1ed

default

Download file

             urls.txt
        
                    66 lines
            
             | 2.3 KiB
            
                | text/plain
            
             |
                TextLexer

/ mercurial / help / urls.txt

History | Source | Raw |Copy content |Copy permalink

Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999	Valid URLs are of the form::

		local/filesystem/path[#revision]
Mads Kiilerich help: Backed out changeset e99facd2cd2a, description of file urls...	r15533	file://local/filesystem/path[#revision]
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999	http://[user[:pass]@]host[:port]/[path][#revision]
		https://[user[:pass]@]host[:port]/[path][#revision]
Matt Mackall help: ssh urls don't allow passwords	r13304	ssh://[user@]host[:port]/[path][#revision]
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		Paths in the local filesystem can either point to Mercurial
Mike Williams help: stop documentation markup appearing in generated help...	r19197	repositories or to bundle files (as created by :hg:`bundle` or
		:hg:`incoming --bundle`). See also :hg:`help paths`.
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		An optional identifier after # indicates a particular branch, tag, or
Martin Geisler Use hg role in help strings	r10973	changeset to use from the remote repository. See also :hg:`help
		revisions`.
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		Some features, such as pushing to http:// and https:// URLs are only
		possible if the feature is explicitly enabled on the remote Mercurial
		server.

Mads Kiilerich doc: clarify that https cert verification requires web.cacerts	r12593	Note that the security of HTTPS URLs depends on proper configuration of
		web.cacerts.

Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999	Some notes about using SSH with Mercurial:

		- SSH requires an accessible shell account on the destination machine
Josef 'Jeff' Sipek help: fix wording describing SSH requirements	r36372	and a copy of hg in the remote path or specified with remotecmd.
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999	- path is relative to the remote user's home directory by default. Use
		an extra slash at the start of a path to specify an absolute path::

		ssh://example.com//tmp/repository

		- Mercurial doesn't use its own compression via SSH; the right thing
		to do is to configure it in your ~/.ssh/config, e.g.::

		Host *.mylocalnetwork.example.com
		Compression no
		Host *
		Compression yes

Brodie Rao help: refer to user configuration file more consistently...	r12083	Alternatively specify "ssh -C" as your ssh command in your
		configuration file or with the --ssh command line option.
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
Brodie Rao help: refer to user configuration file more consistently...	r12083	These URLs can all be stored in your configuration file with path
		aliases under the [paths] section like so::
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		[paths]
		alias1 = URL1
		alias2 = URL2
		...

		You can then use the alias for any command that uses a URL (for
Martin Geisler Use hg role in help strings	r10973	example :hg:`pull alias1` will be treated as :hg:`pull URL1`).
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		Two path aliases are special because they are used as defaults when
		you do not provide the URL to a command:

		default:
		When you create a repository with hg clone, the clone command saves
		the location of the source repository as the new repository's
		'default' path. This is then used when you omit path from push- and
		pull-like commands (including incoming and outgoing).

		default-push:
		The push command will look for a path named 'default-push', and
		prefer it over 'default' if both are defined.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages