Brian Kroth

icon indicating a website link https://bpkroth.github.io

icon company @Microsoft-CISL icon location Madison, WI icon location All around geek. Work with UW-Madison at the Microsoft @GraySystemsLab on data systems research and development.

Results 89 comments of Brian Kroth

mlos_bench: improved failure handling

See also #523

Consider using `os.path.samefile` for path comparisons in tests

FWIW, I don't think this works for files that don't actually exist.

Better naming for `config` and `params` in VM and SaaS-related services

One instance of this mismatch: in `remote_exec()` we take `config` but in `start_host()` we take `params`. - [ ] Both should probably be `params`

mlos_bench storage: track config actually run and other basic system metadata

Additional things that would be good to capture by default: - OS version - VM specs (CPU type, nominal speed, core count, geometry, RAM size, etc.)

mlos_bench storage: track config actually run and other basic system metadata

Related: https://thehftguy.com/2023/11/14/the-linux-kernel-has-been-accidentally-hardcoded-to-a-maximum-of-8-cores-for-nearly-20-years/

Create a multi-VM example for Azure

See Also: - #329 - #332

Create a multi-VM example for Azure

#455 does this

Create a multi-VM example for Azure

Nm, I guess that was still just single VM.

mlos_bench: improve relative paths in configs

Added some initial work on this here: https://github.com/microsoft/MLOS/compare/main...bpkroth:local-path-resolution-improvements, but it will require some signature changes in many places, so will come back to it another time.

mlos_bench: implement optional early abort logic for time based trials

Some additional notes: In cases of throughput or latency based benchmarks, it's not totally clear how to detect whether a specific trial is worse than a previous one, since some...