Compare commits
9 commits
13074ee836
...
7410c1ff20
| Author | SHA1 | Date | |
|---|---|---|---|
| 7410c1ff20 | |||
| 9626dd6e3c | |||
| 5ef3dbbeee | |||
| 15dc384d78 | |||
| dfcf014303 | |||
| ee3d05f270 | |||
| ed6c192d9a | |||
| 654630a692 | |||
| d1fdf2d876 |
8 changed files with 33 additions and 2 deletions
1
31144ca83f6f3de1a9e3db651b70a8b4/done_time
Normal file
1
31144ca83f6f3de1a9e3db651b70a8b4/done_time
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
2025-07-22T20:37:03.829541278-06:00
|
||||||
|
|
@ -1 +1 @@
|
||||||
inprogress
|
done
|
||||||
1
478ac34c204be06b1da5b4f0b5a2532d/assignee
Normal file
1
478ac34c204be06b1da5b4f0b5a2532d/assignee
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
seb
|
||||||
|
|
@ -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
|
||||||
|
<https://profiler.firefox.com/>.
|
||||||
|
|
||||||
|
A local visualizer would be nice, i'm sure there is one somewhere.
|
||||||
1
478ac34c204be06b1da5b4f0b5a2532d/done_time
Normal file
1
478ac34c204be06b1da5b4f0b5a2532d/done_time
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
2025-07-22T20:47:14.363750382-06:00
|
||||||
|
|
@ -1 +1 @@
|
||||||
backlog
|
done
|
||||||
|
|
@ -0,0 +1,10 @@
|
||||||
|
Yeah that red blob 🛑 is super heavy, and the octagonal shape is pretty
|
||||||
|
subtle - it looks more like a stop light than a stop sign.
|
||||||
|
|
||||||
|
I like your thought of somehow showing the state of the issues we
|
||||||
|
dependend on... How about showing the count of not-Done dependencies?
|
||||||
|
And once all the dependencies are Done, not showing the ↖ or ⌛ or
|
||||||
|
whatever at all.
|
||||||
|
|
||||||
|
In the `ent show` output we could list all dependencies with a ↖ or
|
||||||
|
⌛ for the not-Done ones and a ✅ for the Done ones.
|
||||||
Loading…
Add table
Add a link
Reference in a new issue