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

Jump to bottom

Instrument internal timing measures #50

Closed
facundobatista opened this issue Jun 24, 2020 · 1 comment
Closed

Instrument internal timing measures #50

facundobatista opened this issue Jun 24, 2020 · 1 comment
Labels
Enhancement New feature or request

Comments

@facundobatista
Copy link
Contributor

We need to always be able to distinguish:

  • bootstrap time (which can be improved deferring crazy imports, etc): this is until we're ready to call the commands' .run
  • proper command time (which would need to be improved on a per command basis): this is from calling 'run to its end
  • external interaction times (to be substracted from above's times, and properly informed to external parties): so far we only have interaction with the Store, but we may have other network backends in the future, or even local ones (services in the developer machine).
@chipaca chipaca added the Enhancement New feature or request label Oct 14, 2020
@facundobatista
Copy link
Contributor Author

Timings in general have not been a problem, except for the pack operation, for which we opened the #690 issue with more specific ideas and details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@facundobatista @chipaca