From 205a2635cd2221ece441e6996b733e4dc8ae0c49 Mon Sep 17 00:00:00 2001 From: Sebastian Kuzminsky Date: Tue, 22 Jul 2025 14:03:22 -0600 Subject: [PATCH] edit comment 6ce4f668904c7016c846bcc9c0429aca on issue FIXME --- .../comments/6ce4f668904c7016c846bcc9c0429aca/description | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/87fa3146b90db61c4ea0de182798a0e5/comments/6ce4f668904c7016c846bcc9c0429aca/description b/87fa3146b90db61c4ea0de182798a0e5/comments/6ce4f668904c7016c846bcc9c0429aca/description index 339771b..ec71a9a 100644 --- a/87fa3146b90db61c4ea0de182798a0e5/comments/6ce4f668904c7016c846bcc9c0429aca/description +++ b/87fa3146b90db61c4ea0de182798a0e5/comments/6ce4f668904c7016c846bcc9c0429aca/description @@ -8,8 +8,9 @@ I've reducted this a bit (in the `speed-test` git branch) by running 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, +need to. For example, if we're trying to look up the tags of 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. +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. +I've verified that this makes ent *very* fast.