perf: add filter for urns in bench data

[supermaxiste]

Proposed Changes

F

Types of Changes

What types of changes does your code introduce? Put an x in the boxes that
apply

• A bug fix (non-breaking change which fixes an issue).
• A new feature (non-breaking change which adds functionality).
• A breaking change (fix or feature that would cause existing
  functionality to not work as expected).
• A non-productive update (documentation, tooling, etc. if none of the
  other choices apply).

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask. We're here to
help! This is simply a reminder of what we are going to look for before merging
your code.

• I have read the
  CONTRIBUTING
  guidelines.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added the necessary documentation (if appropriate).

Further Comments

[github-actions]

tripsu profiling

date: 2025-07-21

Comparing  against main.

Timings

Run time compared using hyperfine

Indexing

Command	Mean [s]	Min [s]	Max [s]	Relative
main	1.465 ± 0.003	1.462	1.470	1.00
HEAD	1.467 ± 0.005	1.460	1.475	1.00 ± 0.00

Pseudonymization

Command	Mean [s]	Min [s]	Max [s]	Relative
main	5.283 ± 0.020	5.264	5.316	1.01 ± 0.01
HEAD	5.245 ± 0.037	5.214	5.303	1.00

Memory

Heap memory usage compared using heaptrack

Indexing

main: peak heap memory consumption: 13.57M
HEAD: peak heap memory consumption: 13.57M

Pseudonymization

main: peak heap memory consumption: 14.19M
HEAD: peak heap memory consumption: 14.19M