Compiler Enhancements
Optimized compilation and context resolution
This version brings several new heuristics to optimize the process of resolving and converting Polyaxonfiles, from a couple of milliseconds to a second in some cases, which should translate to faster scheduling of operations.
We also consolated the interface for requesting and resolving information from the compiler’s context, as well as moving the context to its own documentation section.
Improved init artifacts specification
This was requested several times, extending the artifacts initializer to allow providing a custom destination path where it should store the artifacts collected:
init:
files:
- file1
- - file2
- path/to/store/file2
dirs:
- dir1
- - dir2
- path/to/store/dir2
file1
and dir1
are what users were familiar with. file2
and dir2
are the new capability, the initializer accepts a tuple to specify the path from and the path to.
Restart with copy improvement
As a result of the previous enhancement, when a user restarts an operation using the copy mode, the copied information will be initialized automatically under the new run.
Note: Restart with copy mode is an advanced feature to allow users to resume training of an experiment with updated code/params/configuration/resources multiple times without mutating the original run.
New input type UUID
Polyaxonfile parser can now validate uuid
types properly, users can use this new type instead of str
to validate the inputs and fail faster.
Learn More about Polyaxon
This blog post just goes over a couple of features that we shipped since our last product update, there are several other features and fixes that are worth checking. To learn more about all the features, fixes, and enhancements, please visit the release notes.
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.