Compare commits

..

No commits in common. "7410c1ff20d9bc799c017403dfdec34998a3614f" and "13074ee836a8e6d8572cf3823b0692616169ba07" have entirely different histories.

8 changed files with 2 additions and 33 deletions

View file

@ -1 +0,0 @@
2025-07-22T20:37:03.829541278-06:00

View file

@ -1 +1 @@
done
inprogress

View file

@ -1 +0,0 @@
seb

View file

@ -1,18 +0,0 @@
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.

View file

@ -1 +0,0 @@
2025-07-22T20:47:14.363750382-06:00

View file

@ -1 +1 @@
done
backlog

View file

@ -1,10 +0,0 @@
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.