- Newest
- Most votes
- Most comments
If the logic for logging of individual frames is implemented and displayed on the the Studio UI, it would have been the cause of the "degraded" performance on Amazon SageMaker Studio.
As the actual inference is done in the backend, every frame to be logged has to send back to the Studio UI to be displayed. The volume of the logs could have been too much that the Studio UI could not display them out quick enough when they are being transported back from the backend to the frontend, hence the delay. So in actual fact, the inference was actually completed. Do expect the time taken for the inference to be completed to be the same as Google Colab and (if possible) check the output directory for the output generated.
Workaround: to reduce the number of logs printed on Studio UI. Instead of logging it frame-by-frame, do so every 50 or 100 frames.
A ticket has been raised and this bug in the Studio UI should see a fix. Any updates would be posted here.
Relevant content
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
Hi, you should open a ticket via AWS console to see this one fixed: service teams are not supposed to monitor re:Post for bug reports.