From 15dc384d782351097645fadf0588b0deac37e371 Mon Sep 17 00:00:00 2001 From: Sebastian Kuzminsky Date: Tue, 22 Jul 2025 20:45:59 -0600 Subject: [PATCH] add comment af965d012390c5c18c16a94f0714e720 on issue 478ac34c204be06b1da5b4f0b5a2532d --- .../description | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 478ac34c204be06b1da5b4f0b5a2532d/comments/af965d012390c5c18c16a94f0714e720/description diff --git a/478ac34c204be06b1da5b4f0b5a2532d/comments/af965d012390c5c18c16a94f0714e720/description b/478ac34c204be06b1da5b4f0b5a2532d/comments/af965d012390c5c18c16a94f0714e720/description new file mode 100644 index 0000000..3b1391b --- /dev/null +++ b/478ac34c204be06b1da5b4f0b5a2532d/comments/af965d012390c5c18c16a94f0714e720/description @@ -0,0 +1,18 @@ +I added a simple performance-measuring tool, `tools/time-ent`. It runs +ent a couple of different ways, against a known entomologist-data branch +(specified by a commit in the regular entomologist-data branch in this +repo). That script gives a rough, over-all measurement of how long +different ent commands take. + +More detailed information, including the call tree and flame graph, +can be gathered like this: + +``` +$ perf record -g -F 999 ent tag 7e2a3a59fb6b77403ff1035255367607 +$ perf script -F +pid > /tmp/test.perf +``` + +Then upload the `test.perf` file to the firefox visualizer at +. + +A local visualizer would be nice, i'm sure there is one somewhere.