git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] p1400: Use `git-update-ref --stdin` to test multiple transactions

From
Jeff King <peff@peff.net>
Date
Nov 5, 2020, 19:34 UTC
Message-ID
<20201105193455.GB121650@coredump.intra.peff.net>
In-Reply-To
<bfaac619112b04aa6545f229ea60433cbf8da73a.1604501265.git.ps@pks.im>
On Wed, Nov 04, 2020 at 03:57:22PM +0100, Patrick Steinhardt wrote:
Show 11 quoted lines
> In commit 0a0fbbe3ff (refs: remove lookup cache for
> reference-transaction hook, 2020-08-25), a new benchmark was added to
> p1400 which has the intention to exercise creation of multiple
> transactions in a single process. As git-update-ref wasn't yet able to
> create multiple transactions with a single run we instead used git-push.
> As its non-atomic version creates a transaction per reference update,
> this was the best approximation we could make at that point in time.
> 
> Now that `git-update-ref --stdin` supports creation of multiple
> transactions, let's convert the benchmark to use that instead. It has
> less overhead and it's also a lot clearer what the actual intention is.
Good direction. The diff confused me for a moment...
Show 14 quoted lines
> @@ -26,14 +27,7 @@ test_perf "update-ref" '
>  '
>  
>  test_perf "update-ref --stdin" '
> -	git update-ref --stdin <update &&
> -	git update-ref --stdin <delete &&
> -	git update-ref --stdin <create
> -'
> -
> -test_perf "nonatomic push" '
> -	git push ./target-repo.git $(test_seq 1000) &&
> -	git push --delete ./target-repo.git $(test_seq 1000)
> +	git update-ref --stdin <instructions >/dev/null
>  '

...because we're dropping _two_ tests here. But I think they were testing the same thing, just with varying degrees of quality.

It could possibly be useful to have perf results broken down by operation type (create vs delete vs update), but the original certainly didn't do that. And it's not clear to me it would actually produce interesting results; certainly not related to the hook, but possibly related to benchmarking ref updates in general. So I don't think it's worth worrying about.

-Peff
Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 9 of 41 in “update-ref: Allow creation of multiple transactions”
  1. 0/2 update-ref: Allow creation of multiple transactionsPatrick Steinhardt, Nov 4, 2020
  2. 1/2 update-ref: Allow creation of multiple transactionsPatrick Steinhardt, Nov 4, 2020
  3. Jeff KingNov 5, 2020
  4. Junio C HamanoNov 5, 2020
  5. Jeff KingNov 6, 2020
  6. Junio C HamanoNov 6, 2020
  7. Patrick SteinhardtNov 6, 2020
  8. 2/2 p1400: Use `git-update-ref --stdin` to test multiple transactionsPatrick Steinhardt, Nov 4, 2020
  9. Jeff KingNov 5, 2020
  10. 0/4 update-ref: Allow creation of multiple transactionsPatrick Steinhardt, Nov 9, 2020
  11. 1/4 t1400: Avoid touching refs on filesystemPatrick Steinhardt, Nov 9, 2020
  12. Junio C HamanoNov 9, 2020
  13. Jeff KingNov 9, 2020
  14. Patrick SteinhardtNov 10, 2020
  15. Junio C HamanoNov 10, 2020
  16. 2/4 update-ref: Allow creation of multiple transactionsPatrick Steinhardt, Nov 9, 2020
  17. 3/4 p1400: Use `git-update-ref --stdin` to test multiple transactionsPatrick Steinhardt, Nov 9, 2020
  18. 4/4 update-ref: Disallow restart of ongoing transactionsPatrick Steinhardt, Nov 9, 2020
  19. Junio C HamanoNov 9, 2020
  20. Jeff KingNov 9, 2020
  21. Junio C HamanoNov 9, 2020
  22. 0/4 update-ref: allow creation of multiple transactionsPatrick Steinhardt, Nov 11, 2020
  23. 1/4 t1400: avoid touching refs on filesystemPatrick Steinhardt, Nov 11, 2020
  24. SZEDER GáborNov 11, 2020
  25. Patrick SteinhardtNov 11, 2020
  26. SZEDER GáborNov 11, 2020
  27. Jeff KingNov 11, 2020
  28. Patrick SteinhardtNov 13, 2020
  29. 2/4 update-ref: allow creation of multiple transactionsPatrick Steinhardt, Nov 11, 2020
  30. 3/4 p1400: use `git-update-ref --stdin` to test multiple transactionsPatrick Steinhardt, Nov 11, 2020
  31. 4/4 update-ref: disallow "start" for ongoing transactionsPatrick Steinhardt, Nov 11, 2020
  32. 0/4 update-ref: allow creation of multiple transactionsPatrick Steinhardt, Nov 13, 2020
  33. 1/4 t1400: avoid touching refs on filesystemPatrick Steinhardt, Nov 13, 2020
  34. Jeff KingNov 13, 2020
  35. Patrick SteinhardtNov 18, 2020
  36. Junio C HamanoNov 18, 2020
  37. 2/4 update-ref: allow creation of multiple transactionsPatrick Steinhardt, Nov 13, 2020
  38. 3/4 p1400: use `git-update-ref --stdin` to test multiple transactionsPatrick Steinhardt, Nov 13, 2020
  39. 4/4 update-ref: disallow "start" for ongoing transactionsPatrick Steinhardt, Nov 13, 2020
  40. Junio C HamanoNov 25, 2020
  41. Jeff KingNov 26, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.