TALER-MERCHANT-BENCHMARK(1)

πŸ“¦ version 1.3.0, in nixos 26.05, nixpkgs unstable

πŸ’… TALER-MERCHANT-BENCHMARK(1) πŸ’…

ok so bestie, this one lives in the GNU Taler manual, and it's genuinely such a useful little gremlin of a tool. Let's get into it πŸ’–


✨ NAME ✨

taler-merchant-benchmark β€” literally the tool that generates Taler-style benchmarking payments for you πŸŽ€


🌸 SYNOPSIS 🌸

taler-merchant-benchmark [subcommand] [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

taler-merchant-benchmark is a command-line tool that populates your merchant database with payments, specifically for benchmarking. that's it, that's the whole job, and it does it so well πŸ‘‘


πŸŽ€ SUBCOMMANDS πŸŽ€

  • ordinary β€” generates normal payments: every single payment gets performed (by the default instance, no cap) and then aggregated by the exchange. takes this one option:
    • -p PN, --payments-number=PN β€” perform PN many payments. defaults to 1.
  • corner β€” drives the generator into unusual situations, like for example leaving payments unaggregated, or using a non-default merchant instance. this is the chaos-mode subcommand fr fr. takes these options:
    • -t TC, --two-coins=TC β€” perform TC many payments that use two coins (normally, all the payments use only one coin, so this is the spicy version 🌢️). TC defaults to 1.
    • -u UN, --unaggregated-number=UN β€” generate UN payments that will be left unaggregated.
⚠️ heads up bestie: note that subsequent invocations of the generator may pick those unaggregated payments and actually aggregate them. so like, they're not permanently unaggregated, they're just unaggregated for now, iykyk 😭

πŸ’œ COMMON OPTIONS πŸ’œ

  • -a APIKEY, --apikey=APIKEY β€” the HTTP Authorization header to send to the merchant. your little VIP pass 🎟️
  • -c FILENAME, --config=FILENAME β€” use the configuration and other resources for the merchant to operate from FILENAME.
  • -u SECTION, --exchange-account-section=SECTION β€” the configuration SECTION specifying the exchange account to use. (yes, -u shows up twice in this page with two totally different meanings β€” corner subcommand takes UN, this takes SECTION. iconic of them honestly πŸ’€)
  • -h, --help β€” print short help on options. your safety net 🫢
  • -L LOGLEVEL, --loglevel=LOGLEVEL β€” specifies the log level to use. accepted values are: DEBUG, INFO, WARNING, ERROR.
  • -l FILENAME, --logfile=FILENAME β€” send logging output to FILENAME.
  • -v, --version β€” print version information ⭐

πŸ”₯ SEE ALSO πŸ”₯

taler-merchant-dbinit(1), taler-merchant.conf(5)


πŸ’€ BUGS πŸ’€

report bugs by using https://bugs.taler.net/ or by sending electronic mail to <taler@gnu.org>. they genuinely want to hear from you, no gatekeeping 🌈


πŸ‘‘ AUTHOR πŸ‘‘

GNU Taler contributors 🫢


2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+)


ok and that's the whole thing, bestie β€” version 1.0, dated Dec 22, 2025, from the GNU Taler crew πŸ’– go benchmark something gorgeous, you've got this βœ¨πŸ“

πŸ“¦ where this page comes from