We have started the year off busy improving our products, releasing the following new features, and expanding to new use-cases! We hope you like these enhancements:
A new post-processing step that refines the recommended settings by filtering out knobs that have a minimal effect. This results in fewer but meaner knobs that are different from baseline. We support two methods of refinement:
1. Using a proprietary algorithm, Optimizer Studio quickly finds and filters the least influential knobs, with fewer new measurements.
2. Optimizer Studio measures each knob separately to determine which of the knobs can be filtered out. This requires more measurements, so it has to be turned on explicitly.
Speed up experiments by providing Optimizer Studio with multiple starting points that were obtained in previous runs and experiments. In certain scenarios like continuous optimization or when optimizing a suite of benchmarks, it is desirable to seed Optimizer Studio with several starting points.
Newly embedded JVM tunables allow any Java process to benefit from tailored JRE settings. No more guessing how to configure the garbage collector or the memory parameters.
Users can now run Optimizer Studio and decide to stop for any reason, perhaps for removing outliers or to start on another similar environment with the same workload and conditions, and then resume from the point in which they stopped. The Replay feature enables users to save a lot of time by quickly replaying the already made samples stored in CSV format (by default) and then resuming where they left off.
- Optimizer Studio can now be executed without any arguments as long as the configuration files are in the same directory
- The current log file is reported to the console of the current run
- Knob values can now be accessed as an environment variable as an array in the resulting settings file of an optimization run