tags-cache: skip the filternode step if we are not going to use it When warming the hgtagsfnodescache, we don't need the actual result, so we can simply skip the part that "filter" fnode we read from the cache. So provide a quite visible speed up to the top level `hg debugupdatecache` function. ### data-env-vars.name = mozilla-try-2023-03-22-zstd-sparse-revlog # benchmark.name = hg.debug.debug-update-cache # bin-env-vars.hg.flavor = default # bin-env-vars.hg.py-re2-module = default # benchmark.variants.pre-state = warm before: 19.947581 after: 18.916804 (-5.17%, -1.03)

     1

Test issue2761

     2

     3

  $ hg init repo

     4

  $ cd repo

     5

     6

  $ touch to-be-deleted

     7

  $ hg add

     8

  adding to-be-deleted

     9

  $ hg ci -m first

    10

  $ echo a > to-be-deleted

    11

  $ hg ci -m second

    12

  $ rm to-be-deleted

    13

  $ hg diff -r 0

    14

    15

Same issue, different code path

    16

    17

  $ hg up -C

    18

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    19

  $ touch does-not-exist-in-1

    20

  $ hg add

    21

  adding does-not-exist-in-1

    22

  $ hg ci -m third

    23

  $ rm does-not-exist-in-1

    24

  $ hg diff -r 1