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

ParallelRunStep progress metric #18357

Closed
emepetres opened this issue Apr 27, 2021 · 6 comments
Closed

ParallelRunStep progress metric #18357

emepetres opened this issue Apr 27, 2021 · 6 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Machine Learning ML-Inference AreaPath question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@emepetres
Copy link
Contributor

Is your feature request related to a problem? Please describe.
During a ParallelRunStep execution, It is not possible to know how many items have been processed and how many are left. In long runs, it would be nice to know at least the processed/total metric, to assess its progress and estimation time to finish.

Describe the solution you'd like
I'd like to access through the python api or through the details tab of a ParallelRunStep to the percentage of processed items.

Describe alternatives you've considered
I guess I could parse somehow the logs and create my own tool to compute this metric, but I think this solution is a little bit messy and it would be much more cleaner to access this information from the ML Studio or the API

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 27, 2021
@rakshith91 rakshith91 added Machine Learning Service Attention Workflow: This issue is responsible by Azure service team. labels Apr 27, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 27, 2021
@ghost
Copy link

ghost commented Apr 27, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureml-github.

Issue Details

Is your feature request related to a problem? Please describe.
During a ParallelRunStep execution, It is not possible to know how many items have been processed and how many are left. In long runs, it would be nice to know at least the processed/total metric, to assess its progress and estimation time to finish.

Describe the solution you'd like
I'd like to access through the python api or through the details tab of a ParallelRunStep to the percentage of processed items.

Describe alternatives you've considered
I guess I could parse somehow the logs and create my own tool to compute this metric, but I think this solution is a little bit messy and it would be much more cleaner to access this information from the ML Studio or the API

Author: emepetres
Assignees: -
Labels:

Machine Learning, Service Attention, customer-reported, needs-triage, question

Milestone: -

@rakshith91
Copy link
Contributor

Thanks for the issue! The team will investigate this asap

@v-strudm-msft v-strudm-msft added the ML-Inference AreaPath label Apr 27, 2021
@ghost
Copy link

ghost commented Apr 27, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @shivanissambare.

Issue Details

Is your feature request related to a problem? Please describe.
During a ParallelRunStep execution, It is not possible to know how many items have been processed and how many are left. In long runs, it would be nice to know at least the processed/total metric, to assess its progress and estimation time to finish.

Describe the solution you'd like
I'd like to access through the python api or through the details tab of a ParallelRunStep to the percentage of processed items.

Describe alternatives you've considered
I guess I could parse somehow the logs and create my own tool to compute this metric, but I think this solution is a little bit messy and it would be much more cleaner to access this information from the ML Studio or the API

Author: emepetres
Assignees: -
Labels:

ML-Inference, Machine Learning, Service Attention, customer-reported, question

Milestone: -

@shivanissambare
Copy link

@tracychms please help with this issue
thank you!

@tracychms
Copy link

Thanks for the feedback. In Studio, if you go to the step's Metrics tab, you will be able to see a chart/table of execution progress, including remaining items, remaining mini batches, failed items, etc.

@emepetres
Copy link
Contributor Author

That's great thanks!

azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this issue Apr 15, 2022
Review request for Microsoft.ContainerService to add version 2022-03-01 (Azure#18686)

* Adds base for updating Microsoft.ContainerService from version stable/2022-02-01 to version 2022-03-01

* Updates readme

* Updates API version in new specs and examples

* Update readmes for the 2022-03-01 dev branch of container service (Azure#18357)

* update readme

* update sdk readmes

* feat: add ManagedCluster StorageProfile in 0301 (Azure#18594)

Signed-off-by: Ji An Liu <jiliu8@microsoft.com>

* Replace common type definitions with references since 2022-03-01 for Microsoft.ContainerService (Azure#18568)

* replace Resource

* replacing systemData

* replace parameters

* fix: replace Resource with TrackedResource

* replace track2 with python

Co-authored-by: Ji'an Liu <jiliu8@microsoft.com>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Machine Learning ML-Inference AreaPath question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

5 participants