Compare commits
5 commits
b0b14187c1
...
a2717f4a55
| Author | SHA1 | Date | |
|---|---|---|---|
| a2717f4a55 | |||
| f81eb4845c | |||
| d0a23dc654 | |||
| 6ddd800ab1 | |||
| ea871643af |
4 changed files with 18 additions and 1 deletions
1
31144ca83f6f3de1a9e3db651b70a8b4/assignee
Normal file
1
31144ca83f6f3de1a9e3db651b70a8b4/assignee
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
seb
|
||||||
|
|
@ -1 +1 @@
|
||||||
backlog
|
inprogress
|
||||||
|
|
@ -0,0 +1,15 @@
|
||||||
|
`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
87fa3146b90db61c4ea0de182798a0e5/state
Normal file
1
87fa3146b90db61c4ea0de182798a0e5/state
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
backlog
|
||||||
Loading…
Add table
Add a link
Reference in a new issue