Skip to content
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.

Investigate breakpoint capture performance #71

Closed
matthewloring opened this issue Jan 13, 2016 · 2 comments
Closed

Investigate breakpoint capture performance #71

matthewloring opened this issue Jan 13, 2016 · 2 comments
Assignees
@matthewloring
Labels
api: clouddebugger Issues related to the googleapis/cloud-debug-nodejs API. 🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@matthewloring
Copy link
Contributor

No description provided.

@matthewloring matthewloring mentioned this issue Jan 14, 2016
Merged
@matthewloring
Copy link
Contributor Author

On my local machine using Node v5.3.x, breakpoints were captured in ~5-7ms depending on the size of watch expressions computed. Breakpoints were reported to the API in another 2-4ms for a total of 7-11ms. Unfortunately, on versions of Node before 1.6, variable resolution takes roughly 10x longer due to nodejs/node#1190. Unfortunately, on travis these captures take as much as 250ms and so the test introduced to monitor performance in #73 won't be run with unit tests on each PR.

@matthewloring
Copy link
Contributor Author

Closing this now that we have some data. We can revisit at a later time.

@google-cloud-label-sync google-cloud-label-sync bot added the api: clouddebugger Issues related to the googleapis/cloud-debug-nodejs API. label Jan 31, 2020
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@matthewloring matthewloring

Labels
api: clouddebugger Issues related to the googleapis/cloud-debug-nodejs API. 🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matthewloring @yoshi-automation