You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello,I wonder if I can get an ET or some other information that can be used to generate chakra before the actual execution of the program, as I saw “We extended PyTorch to support trace collection with the Execution Graph Observer [1], which does not require intrusive modifications to ML models. Simply enabling the Execution Graph Observer before running a model yields traces that closely reflect real-world execution.” when I read the paper ,
but in the example,
the code use ExecutionTraceObserver instead of Execution Graph Observer,I think I only got the profile information after actually running the code here, whether to abandon the use of the Execution Graph Observer
The text was updated successfully, but these errors were encountered:
The converter only supports these schemas,and the schema comes from pytorch_et.json, why does the pytorch profile appear like "1.0.2-chakra.0.0.4", "1.0.3-chakra.0.0.4", "1.1.0-chakra.0.0.4" Version
hello,I wonder if I can get an ET or some other information that can be used to generate chakra before the actual execution of the program, as I saw “We extended PyTorch to support trace collection with the Execution Graph Observer [1], which does not require intrusive modifications to ML models. Simply enabling the Execution Graph Observer before running a model yields traces that closely reflect real-world execution.” when I read the paper ,
![image](https://private-user-images.githubusercontent.com/80091648/387981823-8887e91d-c492-4f50-a870-fe50db1b525d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNDQxNDQsIm5iZiI6MTczOTI0Mzg0NCwicGF0aCI6Ii84MDA5MTY0OC8zODc5ODE4MjMtODg4N2U5MWQtYzQ5Mi00ZjUwLWE4NzAtZmU1MGRiMWI1MjVkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDAzMTcyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE3NjhlZDA1OWVkZWI5MDU5Nzc3MGUxM2Q3YjM3OGEzYjQwY2ZiMTA0YWE3ZDBhMGRhNWFjNjlhMzIzYjM5OTcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.IXI8rQ6Vf6vxs4IKMxWjE9LwOtwA5eRSoaKWLQTnImY)
but in the example,
the code use ExecutionTraceObserver instead of Execution Graph Observer,I think I only got the profile information after actually running the code here, whether to abandon the use of the Execution Graph Observer
The text was updated successfully, but these errors were encountered: