Open sqs opened 8 months ago
This issue is marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed automatically in 5 days.
This issue is marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed automatically in 5 days.
Not stale?
tl;dr I looked into vscode cody's slow activation time and it appears we aren't doing anything wrong/dumb, and it only gets slow if there are a lot of other extensions as well (we get dinged because s, the first letter of our extension ID, is lower in the alphabet than most extensions)
I saw that VS Code's
Developer > Show Running Extensions
was saying Cody was taking 2-3 seconds to activate. I looked into this. Here are my notes.onStartupFinished
activationEvents in their package.json are loaded after everything else in VS Code. When I disable GitHub Copilot and Copilot Chat (which also useonStartupFinished
), our activation time as reported byDeveloper > Show Running Extensions
drops from 2-3s to ~600ms, which is almost exactly whatDeveloper > Show Running Extensions
reported for GitHub Copilot and Copilot Chat before I disabled them. This makes me think that VS Code loadsonStartupFinished
extensions in alphabetical order or something (I haven't confirmed this).Timings
before:
w/o copilot+ocg:
w/o ocg:
w/o copilot+copilotchat+ocg:
w/ 1.1MB memento instead of 1.8MB:
mementoTP set 22.5ms
w/ 1kb memento
cody-start: 1.53s
show running extensions: 604ms
mementoTP: set 1.5ms
Diffs I used to get these timings: