microsoft / microsoft/vscode-documentdb
Extension Activation Time Appears Longer Than Expected
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 22
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 21
Description
Extension Activation Time Appears Longer Than Expected
We've observed that our extension's activation time is noticeably longer compared to other extensions. This could impact user experience, especially during startup or reload scenarios.
Tasks
-
Analyze Activation Code Path
Review the extension's activation sequence to identify which parts contribute most to the delay. -
Benchmark Against Other Extensions
Compare our activation time with similar extensions to determine if the delay is within a reasonable range. -
Identify Optimization Opportunities
Assess whether any parts of the activation process can be deferred, parallelized, or otherwise optimized. -
Document Findings
If performance issues are confirmed, update this issue with:- A breakdown of the activation steps and their durations
- Specific areas for improvement
- Suggested actions and their estimated complexity
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by profiling the extension's activation sequence and comparing its timing with similar extensions. Done means documenting activation-step durations, confirmed performance findings, improvement areas, suggested actions, and estimated complexity in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100