Polyaxon v1.11 builds on top of the previous enhancements in dashboards and adds several new features that we shared in this blog post.
This new release also brings also several new inspection, monitoring, and container debugging capabilties, and a new logging interface and featues.
stream improvements
The streams service was reworked to provide faster loading of events:
- The streams logic has a much higher concurrency of events loading for all backends: volumes, paths, S3, GCS, Azure blob storage, …
- Improved cache access and logic for loading artifacts as well as listing
Improved syncing logic in sidecars
Polyaxon sidecar received the necessary improvements to:
- Handle deletion
- Prevent re-uploading artifacts that were initialized in the init containers
- Preserve creation/edition time of artifacts
- Reuse clients’ connections
Enabling/Disabling operation approval from CLI
Polyaxon allows putting an operation on hold until it’s approved by a user using the isApproved section in the Polyaxonfile specification.
This release allows to trigger approval directly from the CLI using a new flag --approved:
polyaxon run --approved=y/yes/t/true/1 ...Or
polyaxon run --approved=n/no/f/false/0 ...Learn More about Polyaxon
This blog post just goes over a couple of features that we shipped in v1.11. To learn more about all the features, fixes, and enhancements, please visit the release notes and the short term roadmap.
Polyaxon continues to grow quickly and keeps improving and providing the simplest machine learning abstraction. We hope that these updates will improve your workflows and increase your productivity, and again, thank you for your continued feedback and support.
