mlos-core
This directory contains the code for the mlos-core optimizer package.
It's available for pip install via the pypi repository at mlos-core.
Description
mlos-core is an optimizer package, wrapping other libraries like FLAML and SMAC to use techniques like Bayesian optimization and others to identify & sample tunable configuration parameters and propose optimal parameter values with a consistent API: suggest and register.
These can be evaluated by mlos-bench, generating and tracking experiment results (proposed parameters, benchmark results & telemetry) to update the optimization loop, or used independently.
Features
Since the tunable parameter search space is often extremely large, mlos-core automates the following steps to efficiently generate optimal task-specific kernel and application configurations.
- Reduce the search space by identifying a promising set of tunable parameters
- Map out the configuration search space: Automatically track and manage the discovery of new Linux kernel parameters and their default values across versions. Filter out non-tunable parameters (e.g., not writable) and track which kernel parameters exist for a given kernel version.
- Leverage parameter knowledge for optimization: Information on ranges, sampling intervals, parameter correlations, workload type sensitivities for tunable parameters are tracked and currently manually curated. In the future, this can be automatically maintained by scraping documentation pages on kernel parameters.
- Tailored to application: Consider prior knowledge of the parameter's impact & an application's workload profile (e.g. network heavy, disk heavy, CPU bound, multi-threaded, latency sensitive, throughput oriented, etc.) to identify likely impactful candidates of tunable parameters, specific to a particular application.
- Sampling to warm-start optimization in a high dimensional search space
- Produce optimal configurations through Bayesian optimization
- Support for various optimizer algorithms (default Bayesian optimizer, Flaml, SMAC, and random for baseline comparison), that handle multiple types of constraints. This includes cost-aware optimization, that considers experiment costs given current tunable parameters.
- Integrated with
mlos-bench, proposed configurations are logged and evaluated.
See Also
- https://microsoft.github.io/MLOS/autoapi/mlos_core/ for more documentation details
Metadata
Release files for mlos-core 0.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mlos_core-0.6.2.tar.gz | 34.0 kB | Without provenance | Details for mlos_core-0.6.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mlos_core-0.6.2-py3-none-any.whl | Python 3 | none | any | Details for mlos_core-0.6.2-py3-none-any.whl |
Total release size: 74.3 kB
Release files / mlos_core-0.6.2.tar.gz
| Download URL | mlos_core-0.6.2.tar.gz |
|---|---|
| Size | 34.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e60997f18cf27a7944dc11252003627246f42130944599f06d5863a7e9cafb60
|
|
BLAKE2b-256 checksum How to use checksums |
01d004a212b2cbe6912a10045022bee2144dc816e09559c57870e3a2c26ae9f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Release files / mlos_core-0.6.2-py3-none-any.whl
| Download URL | mlos_core-0.6.2-py3-none-any.whl |
|---|---|
| Size | 40.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e21179398b19a9dc4d4ece68c0a1e3ffdef9a0ea5f47003375fc014101636a3a
|
|
BLAKE2b-256 checksum How to use checksums |
1a8d71ff0e2075e1ec53097861c7fec8d93b1052108f0846eca68fc286b12ae8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Security for mlos-core 0.6.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.