Compare commits
No commits in common. "a2717f4a5576f389f92028b6180bbb87b8c414f0" and "b0b14187c193503eac47af54422470992feea199" have entirely different histories.
a2717f4a55
...
b0b14187c1
4 changed files with 1 additions and 18 deletions
|
|
@ -1 +0,0 @@
|
||||||
seb
|
|
||||||
|
|
@ -1 +1 @@
|
||||||
inprogress
|
backlog
|
||||||
|
|
@ -1,15 +0,0 @@
|
||||||
`perf` shows that the majority of the time it takes to run "ent anything"
|
|
||||||
is spent reading the issue database, and the majority of the time it
|
|
||||||
takes to read the database is spend running `git log` to find the author
|
|
||||||
and ctime of issues and comments.
|
|
||||||
|
|
||||||
I've reducted this a bit (in the `speed-test` git branch) by running
|
|
||||||
`git log` half as many times, but the shape of the flame graph remains
|
|
||||||
the same.
|
|
||||||
|
|
||||||
We've discussed lazy-loading things to avoid doing this work when we don't
|
|
||||||
need to. For example, if we're trying to look up the tags off issue A,
|
|
||||||
there's no need to ingest all the comments of issue B.
|
|
||||||
|
|
||||||
Another option is to store Author and Creation-time the normal way,
|
|
||||||
as files in the issue directory. We'd never have to run `git log` at all.
|
|
||||||
|
|
@ -1 +0,0 @@
|
||||||
backlog
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue