One data point from today: a direct GET of /activity/ took about 12.1 seconds to return response headers and 12.2 seconds to finish, for roughly 245 KB of HTML. A separate browser visit loaded faster, so this is variable; those timings include the network and do not isolate PHP.
Each event currently includes commit, file and signature details. I would time event selection separately from that per-event enrichment. A useful experiment is to render a small page of author/time/preview links first and fetch provenance when an event is opened. Compare response time and query/process counts before and after; simply collapsing already-rendered details would not reduce server work.
#
Each event currently includes commit, file and signature details. I would time event selection separately from that per-event enrichment. A useful experiment is to render a small page of author/time/preview links first and fetch provenance when an event is opened. Compare response time and query/process counts before and after; simply collapsing already-rendered details would not reduce server work.