##// END OF EJS Templates
localrepo: experimental support for non-zlib revlog compression...
localrepo: experimental support for non-zlib revlog compression The final part of integrating the compression manager APIs into revlog storage is the plumbing for repositories to advertise they are using non-zlib storage and for revlogs to instantiate a non-zlib compression engine. The main intent of the compression manager work was to zstd all of the things. Adding zstd to revlogs has proved to be more involved than other places because revlogs are... special. Very small inputs and the use of delta chains (which are themselves a form of compression) are a completely different use case from streaming compression, which bundles and the wire protocol employ. I've conducted numerous experiments with zstd in revlogs and have yet to formalize compression settings and a storage architecture that I'm confident I won't regret later. In other words, I'm not yet ready to commit to a new mechanism for using zstd - or any other compression format - in revlogs. That being said, having some support for zstd (and other compression formats) in revlogs in core is beneficial. It can allow others to conduct experiments. This patch introduces *highly experimental* support for non-zlib compression formats in revlogs. Introduced is a config option to control which compression engine to use. Also introduced is a namespace of "exp-compression-*" requirements to denote support for non-zlib compression in revlogs. I've prefixed the namespace with "exp-" (short for "experimental") because I'm not confident of the requirements "schema" and in no way want to give the illusion of supporting these requirements in the future. I fully intend to drop support for these requirements once we figure out what we're doing with zstd in revlogs. A good portion of the patch is teaching the requirements system about registered compression engines and passing the requested compression engine as an opener option so revlogs can instantiate the proper compression engine for new operations. That's a verbose way of saying "we can now use zstd in revlogs!" On an `hg pull` conversion of the mozilla-unified repo with no extra redelta settings (like aggressivemergedeltas), we can see the impact of zstd vs zlib in revlogs: $ hg perfrevlogchunks -c ! chunk ! wall 2.032052 comb 2.040000 user 1.990000 sys 0.050000 (best of 5) ! wall 1.866360 comb 1.860000 user 1.820000 sys 0.040000 (best of 6) ! chunk batch ! wall 1.877261 comb 1.870000 user 1.860000 sys 0.010000 (best of 6) ! wall 1.705410 comb 1.710000 user 1.690000 sys 0.020000 (best of 6) $ hg perfrevlogchunks -m ! chunk ! wall 2.721427 comb 2.720000 user 2.640000 sys 0.080000 (best of 4) ! wall 2.035076 comb 2.030000 user 1.950000 sys 0.080000 (best of 5) ! chunk batch ! wall 2.614561 comb 2.620000 user 2.580000 sys 0.040000 (best of 4) ! wall 1.910252 comb 1.910000 user 1.880000 sys 0.030000 (best of 6) $ hg perfrevlog -c -d 1 ! wall 4.812885 comb 4.820000 user 4.800000 sys 0.020000 (best of 3) ! wall 4.699621 comb 4.710000 user 4.700000 sys 0.010000 (best of 3) $ hg perfrevlog -m -d 1000 ! wall 34.252800 comb 34.250000 user 33.730000 sys 0.520000 (best of 3) ! wall 24.094999 comb 24.090000 user 23.320000 sys 0.770000 (best of 3) Only modest wins for the changelog. But manifest reading is significantly faster. What's going on? One reason might be data volume. zstd decompresses faster. So given more bytes, it will put more distance between it and zlib. Another reason is size. In the current design, zstd revlogs are *larger*: debugcreatestreamclonebundle (size in bytes) zlib: 1,638,852,492 zstd: 1,680,601,332 I haven't investigated this fully, but I reckon a significant cause of larger revlogs is that the zstd frame/header has more bytes than zlib's. For very small inputs or data that doesn't compress well, we'll tend to store more uncompressed chunks than with zlib (because the compressed size isn't smaller than original). This will make revlog reading faster because it is doing less decompression. Moving on to bundle performance: $ hg bundle -a -t none-v2 (total CPU time) zlib: 102.79s zstd: 97.75s So, marginal CPU decrease for reading all chunks in all revlogs (this is somewhat disappointing). $ hg bundle -a -t <engine>-v2 (total CPU time) zlib: 191.59s zstd: 115.36s This last test effectively measures the difference between zlib->zlib and zstd->zstd for revlogs to bundle. This is a rough approximation of what a server does during `hg clone`. There are some promising results for zstd. But not enough for me to feel comfortable advertising it to users. We'll get there...

File last commit:

r30731:b8a188a6 default
r30818:4c0a5a25 default
Show More
templates.txt
192 lines | 5.0 KiB | text/plain | TextLexer
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999 Mercurial allows you to customize output of commands through
Yuya Nishihara
help: use --template to specify existing style...
r21943 templates. You can either pass in a template or select an existing
template-style from the command line, via the --template option.
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
You can customize output for any "log-like" command: log,
Matt Mackall
help: drop reference to glog in templates topic
r21945 outgoing, incoming, tip, parents, and heads.
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
Matt Mackall
help: mention '-T list' in templater topic
r21946 Some built-in styles are packaged with Mercurial. These can be listed
with :hg:`log --template list`. Example usage::
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
Matt Mackall
help: mention '-T list' in templater topic
r21946 $ hg log -r1.0::1.1 --template changelog
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
A template is a piece of text, with markup to invoke variable
expansion::
$ hg log -r1 --template "{node}\n"
b56ce7b07c52de7d5fd79fb89701ea538af65746
Matt Harbison
help: apply the section headings from revsets to templates...
r30730 Keywords
========
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999 Strings in curly braces are called keywords. The availability of
keywords depends on the exact context of the templater. These
keywords are usually available for templating a log-like command:
Patrick Mezard
templates: generate keyword help dynamically
r13585 .. keywordsmarker
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
The "date" keyword does not produce human-readable output. If you
want to use a date in your output, you can use a filter to process
it. Filters are functions which return a string based on the input
Dirkjan Ochtman
help: point out need for stringification
r10759 variable. Be sure to use the stringify filter first when you're
applying a string-input filter to a list-like input variable.
You can also use a chain of filters to get the desired output::
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999
$ hg tip --template "{date|isodate}\n"
2008-08-21 18:22 +0000
Matt Harbison
help: apply the section headings from revsets to templates...
r30730 Filters
=======
Dan Villiom Podlaski Christiansen
setup: install translation files as package data...
r9999 List of filters:
Patrick Mezard
templatefilters: move doc from templates.txt to docstrings
r13591 .. filtersmarker
Sean Farley
help: add documentation for new template functions
r18465
Note that a filter is nothing more than a function call, i.e.
``expr|filter`` is equivalent to ``filter(expr)``.
Matt Harbison
help: apply the section headings from revsets to templates...
r30730 Functions
=========
Sean Farley
help: add documentation for new template functions
r18465 In addition to filters, there are some basic built-in functions:
Gregory Szorc
help: populate template functions via docstrings...
r24587 .. functionsmarker
Ryan McElroy
templater: introduce word function...
r21846
Matt Harbison
help: merge the various operator sections of revsets, filesets and templates...
r30731 Operators
=========
Matt Harbison
help: apply the section headings from revsets to templates...
r30730
Simon Farnsworth
templater: provide arithmetic operations on integers...
r30115 We provide a limited set of infix arithmetic operations on integers::
+ for addition
- for subtraction
* for multiplication
/ for floor division (division rounded to integer nearest -infinity)
Division fulfils the law x = x / y + mod(x, y).
Yuya Nishihara
help: update template examples to use reST literal syntax...
r28040 Also, for any expression that returns a list, there is a list operator::
Sean Farley
help: add documentation for new template functions
r18465
Yuya Nishihara
help: update template examples to use reST literal syntax...
r28040 expr % "{template}"
Sean Farley
help: add documentation for new template functions
r18465
Yuya Nishihara
help: update template examples to use reST literal syntax...
r28040 As seen in the above example, ``{template}`` is interpreted as a template.
To prevent it from being interpreted, you can use an escape character ``\{``
or a raw string prefix, ``r'...'``.
Yuya Nishihara
templater: take any string literals as template, but not for rawstring (BC)...
r25596
Matt Harbison
help: apply the section headings from revsets to templates...
r30730 Aliases
=======
Yuya Nishihara
templater: load and expand aliases by template engine (API) (issue4842)...
r28957 New keywords and functions can be defined in the ``templatealias`` section of
a Mercurial configuration file::
<alias> = <definition>
Arguments of the form `a1`, `a2`, etc. are substituted from the alias into
the definition.
For example,
::
[templatealias]
r = rev
rn = "{r}:{node|short}"
leftpad(s, w) = pad(s, w, ' ', True)
defines two symbol aliases, ``r`` and ``rn``, and a function alias
``leftpad()``.
Mathias De Maré
help: add example of '[templates]' usage...
r29717 It's also possible to specify complete template strings, using the
``templates`` section. The syntax used is the general template string syntax.
For example,
::
[templates]
nodedate = "{node|short}: {date(date, "%Y-%m-%d")}\n"
defines a template, ``nodedate``, which can be called like::
$ hg log -r . -Tnodedate
Matt Harbison
help: apply the section headings from revsets to templates...
r30730 Examples
========
Sean Farley
help: add documentation for new template functions
r18465 Some sample command line templates:
- Format lists, e.g. files::
$ hg log -r 0 --template "files:\n{files % ' {file}\n'}"
- Join the list of files with a ", "::
$ hg log -r 0 --template "files: {join(files, ', ')}\n"
Hannes Oldenburg
templates: add built-in files() function...
r30008 - Join the list of files ending with ".py" with a ", "::
$ hg log -r 0 --template "pythonfiles: {join(files('**.py'), ', ')}\n"
Martin von Zweigbergk
templater: add separate() template function...
r29085 - Separate non-empty arguments by a " "::
$ hg log -r 0 --template "{separate(' ', node, bookmarks, tags}\n"
Ryan McElroy
templatefilter: add splitlines function...
r21820 - Modify each line of a commit description::
$ hg log --template "{splitlines(desc) % '**** {line}\n'}"
Sean Farley
help: add documentation for new template functions
r18465 - Format date::
$ hg log -r 0 --template "{date(date, '%Y')}\n"
Yuya Nishihara
templater: add optional timezone argument to localdate()...
r26128 - Display date in UTC::
$ hg log -r 0 --template "{localdate(date, 'UTC')|date}\n"
Sean Farley
help: add documentation for new template functions
r18465 - Output the description set to a fill-width of 30::
Yuya Nishihara
help: rewrite template examples to use integer literals where appropriate
r25004 $ hg log -r 0 --template "{fill(desc, 30)}"
Sean Farley
help: add documentation for new template functions
r18465
- Use a conditional to test for the default branch::
$ hg log -r 0 --template "{ifeq(branch, 'default', 'on the main branch',
'on branch {branch}')}\n"
- Append a newline if not empty::
$ hg tip --template "{if(author, '{author}\n')}"
- Label the output for use with the color extension::
$ hg log -r 0 --template "{label('changeset.{phase}', node|short)}\n"
- Invert the firstline filter, i.e. everything but the first line::
$ hg log -r 0 --template "{sub(r'^.*\n?\n?', '', desc)}\n"
Matthew Turk
help: adding example 'extras' printing to 'hg help templates'
r20016
- Display the contents of the 'extra' field, one per line::
Steve Hoelzer
help: fix formatting of template example
r20170 $ hg log -r 0 --template "{join(extras, '\n')}\n"
Durham Goode
help: add ifcontains, revset, and shortest to template help...
r20531
Ryan McElroy
templatekw: introduce active subkeyword from bookmarks keyword...
r25348 - Mark the active bookmark with '*'::
Durham Goode
help: add ifcontains, revset, and shortest to template help...
r20531
Yuya Nishihara
help: rewrite template examples to not use shell escaping...
r25786 $ hg log --template "{bookmarks % '{bookmark}{ifeq(bookmark, active, '*')} '}\n"
Durham Goode
help: add ifcontains, revset, and shortest to template help...
r20531
Matt Harbison
templater: introduce {latesttag()} function to match a pattern (issue4184)...
r26485 - Find the previous release candidate tag, the distance and changes since the tag::
$ hg log -r . --template "{latesttag('re:^.*-rc$') % '{tag}, {changes}, {distance}'}\n"
Durham Goode
help: add ifcontains, revset, and shortest to template help...
r20531 - Mark the working copy parent with '@'::
$ hg log --template "{ifcontains(rev, revset('.'), '@')}\n"
Ryan McElroy
templater: introduce startswith function...
r21821
Yuya Nishihara
templater: switch ctx of list expression to rev of revset() (BC)...
r26234 - Show details of parent revisions::
$ hg log --template "{revset('parents(%d)', rev) % '{desc|firstline}\n'}"
Ryan McElroy
templater: introduce startswith function...
r21821 - Show only commit descriptions that start with "template"::
Yuya Nishihara
help: rewrite template examples to not use shell escaping...
r25786 $ hg log --template "{startswith('template', firstline(desc))}\n"
Ryan McElroy
templater: introduce word function...
r21846
- Print the first word of each line of a commit message::
Yuya Nishihara
help: rewrite template examples to use integer literals where appropriate
r25004 $ hg log --template "{word(0, desc)}\n"