##// END OF EJS Templates
discovery: slowly increase sampling size...
discovery: slowly increase sampling size Some pathological discovery runs can requires many roundtrip. When this happens things can get very slow. To make the algorithm more resilience again such pathological case. We slowly increase the sample size with each roundtrip (+5%). This will have a negligible impact on "normal" discovery with few roundtrips, but a large positive impact of case with many roundtrips. Asking more question per roundtrip helps to reduce the undecided set faster. Instead of reducing the undecided set a linear speed (in the worst case), we reduce it as a guaranteed (small) exponential rate. The data below show this slow ramp up in sample size: round trip | 1 | 5 | 10 | 20 | 50 | 100 | 130 | sample size | 200 | 254 | 321 | 517 | 2 199 | 25 123 | 108 549 | covered nodes | 200 | 1 357 | 2 821 | 7 031 | 42 658 | 524 530 | 2 276 755 | To be a bit more concrete, lets take a very pathological case as an example. We are doing discovery from a copy of Mozilla-try to a more recent version of mozilla-unified. Mozilla-unified heads are unknown to the mozilla-try repo and there are over 1 million "missing" changesets. (the discovery is "local" to avoid network interference) Without this change, the discovery: - last 1858 seconds (31 minutes), - does 1700 round trip, - asking about 340 000 nodes. With this change, the discovery: - last 218 seconds (3 minutes, 38 seconds a -88% improvement), - does 94 round trip (-94%), - asking about 344 211 nodes (+1%). Of course, this is an extreme case (and 3 minutes is still slow). However this give a good example of how this sample size increase act as a safety net catching any bad situations. We could image a steeper increase than 5%. For example 10% would give the following number: round trip | 1 | 5 | 10 | 20 | 50 | 75 | 100 | sample size | 200 | 321 | 514 | 1 326 | 23 060 | 249 812 | 2 706 594 | covered nodes | 200 | 1 541 | 3 690 | 12 671 | 251 871 | 2 746 254 | 29 770 966 | In parallel, it is useful to understand these pathological cases and improve them. However the current change provides a general purpose safety net to smooth the impact of pathological cases. To avoid issue with older http server, the increase in sample size only occurs if the protocol has not limit on command argument size.

File last commit:

r41318:4fab8a7d default
r42546:dbd0fcca default
Show More
hgignore.txt
97 lines | 3.2 KiB | text/plain | TextLexer
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044 Synopsis
FUJIWARA Katsunori
doc: unify section level between help topics...
r17267 ========
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
The Mercurial system uses a file called ``.hgignore`` in the root
directory of a repository to control its behavior when it searches
for files that it is not currently tracking.
Description
FUJIWARA Katsunori
doc: unify section level between help topics...
r17267 ===========
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
The working directory of a Mercurial repository will often contain
files that should not be tracked by Mercurial. These include backup
files created by editors and build products created by compilers.
These files can be ignored by listing them in a ``.hgignore`` file in
the root of the working directory. The ``.hgignore`` file must be
created manually. It is typically put under version control, so that
the settings will propagate to other repositories with push and pull.
An untracked file is ignored if its path relative to the repository
root directory, or any prefix path of that path, is matched against
any pattern in ``.hgignore``.
For example, say we have an untracked file, ``file.c``, at
``a/b/file.c`` inside our repository. Mercurial will ignore ``file.c``
if any pattern in ``.hgignore`` matches ``a/b/file.c``, ``a/b`` or ``a``.
In addition, a Mercurial configuration file can reference a set of
Wagner Bruna
help/hgignore: refer to the builtin help instead of external URLs
r14668 per-user or global ignore files. See the ``ignore`` configuration
key on the ``[ui]`` section of :hg:`help config` for details of how to
configure these files.
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
Wagner Bruna
help/hgignore: refer to the builtin help instead of external URLs
r14668 To control Mercurial's handling of files that it manages, many
commands support the ``-I`` and ``-X`` options; see
:hg:`help <command>` and :hg:`help patterns` for details.
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
Adrian Buehlmann
help: explain effect of .hgignore on tracked files
r17116 Files that are already tracked are not affected by .hgignore, even
if they appear in .hgignore. An untracked file X can be explicitly
added with :hg:`add X`, even if X would be excluded by a pattern
in .hgignore.
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044 Syntax
FUJIWARA Katsunori
doc: unify section level between help topics...
r17267 ======
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
An ignore file is a plain text file consisting of a list of patterns,
with one pattern per line. Empty lines are skipped. The ``#``
character is treated as a comment character, and the ``\`` character
is treated as an escape character.
Mercurial supports several pattern syntaxes. The default syntax used
is Python/Perl-style regular expressions.
To change the syntax used, use a line of the following form::
syntax: NAME
where ``NAME`` is one of the following:
``regexp``
Regular expression, Python/Perl syntax.
``glob``
Shell-style glob.
Valentin Gatien-Baron
match: support rooted globs in hgignore...
r41318 ``rootglob``
A variant of ``glob`` that is rooted (see below).
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
The chosen syntax stays in effect when parsing all patterns that
follow, until another syntax is selected.
Valentin Gatien-Baron
match: support rooted globs in hgignore...
r41318 Neither ``glob`` nor regexp patterns are rooted. A glob-syntax
pattern of the form ``*.c`` will match a file ending in ``.c`` in any
directory, and a regexp pattern of the form ``\.c$`` will do the
same. To root a regexp pattern, start it with ``^``. To get the same
effect with glob-syntax, you have to use ``rootglob``.
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
Durham Goode
help: add documentation on include: and subinclude:...
r25284 Subdirectories can have their own .hgignore settings by adding
``subinclude:path/to/subdir/.hgignore`` to the root ``.hgignore``. See
:hg:`help patterns` for details on ``subinclude:`` and ``include:``.
FUJIWARA Katsunori
doc: add note about pattern rooted/unrooted cases to "hgignore" and "patterns"...
r16504 .. note::
Simon Heimberg
help: remove last occurrences of ".. note::" without two newlines...
r20532
FUJIWARA Katsunori
doc: add note about pattern rooted/unrooted cases to "hgignore" and "patterns"...
r16504 Patterns specified in other than ``.hgignore`` are always rooted.
Please see :hg:`help patterns` for details.
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044 Example
FUJIWARA Katsunori
doc: unify section level between help topics...
r17267 =======
Yun Lee
help: move hgignore man page into built-in help (issue2769)
r14044
Here is an example ignore file. ::
# use glob syntax.
syntax: glob
*.elc
*.pyc
*~
# switch to regexp syntax.
syntax: regexp
^\.pc/