Skip to content

Report time spent in updateGraph #35675

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

Merged
merged 1 commit into from
Jan 8, 2020

Conversation

amcasey
Copy link
Member

@amcasey amcasey commented Dec 13, 2019

Add a response property indicating how much of the elapsed time (from onMessage to doOutput) was spent in updateGraph calls. If there'sno updateGraph call, the property is undefined, to save space (with the downside that it's harder to tell whether a given telemetry event could have had the property).

Fixes #34774

Add a response property indicating how much of the elapsed time (from
`onMessage` to `doOutput`) was spent in `updateGraph` calls.  If there's
no `updateGraph` call, the property is undefined, to save space (with
the downside that it's harder to tell whether a given telemetry event
could have had the property).

Fixes microsoft#34774
@typescript-bot
Copy link
Collaborator

Thanks for the PR! It looks like you've changed the TSServer protocol in some way. Please ensure that any changes here don't break consumers of the current TSServer API. For some extra review, we'll ping @sheetalkamat, @amcasey, @mjbvz, @minestarks for you. Feel free to loop in other consumers/maintainers if necessary

@uniqueiniquity
Copy link
Contributor

Just to clarify - this reflects the time spent in updateGraph during a given request, regardless of whether or not that request actually triggered the updateGraph, right?

@amcasey
Copy link
Member Author

amcasey commented Dec 13, 2019

@uniqueiniquity Yep

@amcasey
Copy link
Member Author

amcasey commented Dec 13, 2019

Note to reviewers: this looks over-engineered for a single property because it used to be for two properties and I decided the second one needed more refinement than would fit in the 3.8 timeframe.

Copy link
Member Author

@amcasey amcasey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Force pushed a rebase. Changes addressing PR feedback are in a separate commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mark TSServer reponses affected by updateGraph calls
5 participants