Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add telemetry for investigation of perf #3299

Closed
greazer opened this issue Jun 21, 2019 · 2 comments
Closed

Add telemetry for investigation of perf #3299

greazer opened this issue Jun 21, 2019 · 2 comments
Assignees

Comments

@greazer
Copy link
Member

greazer commented Jun 21, 2019

first step is to brainstorm what to measure.

@rchiodo
Copy link
Contributor

rchiodo commented Jun 26, 2019

  • Create environment time
  • Jupyter launch time
  • Jupyter connect time
  • Jupyter hidden cell time
  • Jupyter run cell to actual display time (cold start)
  • Jupyter run cell time

@rchiodo rchiodo self-assigned this Jun 26, 2019
@rchiodo
Copy link
Contributor

rchiodo commented Jun 26, 2019

Here's the total list @IanMatthewHuff and I came up with:

  • Code lens acquisition time (this will be averaged over the entire session since it happens so often)
  • DI ctor time
  • Enumerate environments time
  • Jupyter process launch time
  • Jupyter find process to launch time
  • Jupyter wait till idle time
  • Jupyter silent/hidden cell time (our matplotlib theming and directory switching)
  • Jupyter cell execution time
  • Jupyter restart time
  • Jupyter kernel interrupt time
  • Run cell total perceived time (both first time and every time)
  • Webview style update time
  • Variable explorer fetch time
  • Data Viewer web view startup time
  • Data viewer data ready time
  • Plot Viewer web view startup time

@rchiodo rchiodo closed this as completed Aug 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Aug 14, 2019
@microsoft microsoft unlocked this conversation Nov 14, 2020
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 14, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants