Investigate performance/cache regression after GitLab merge - Githubissues

google / triage-party

🎉 Triage Party: massively multi-player GitHub triage 🎉

Apache License 2.0

504 stars 80 forks source link

Investigate performance/cache regression after GitLab merge #226

Closed tstromberg closed 3 years ago

tstromberg commented 3 years ago

I haven't quantified it yet with data -- but I feel like I'm seeing two perhaps related issues since #193 was merged:

CloudSQL cache doesn't seem to be persistent across restarts (long start times)
Startup feels slower

The next step will be to measure the behavior difference across the commits.