On Thu 09-02-23 10:22:31, Johannes Thumshirn wrote: > On 09.02.23 11:06, Hans Holmberg wrote: > > It takes a significant amount of time and trouble to build, run and understand > > benchmarks for these applications. Modeling the workloads using fio > > minimizes the set-up work and would enable more developers to actually > > run these things. The workload definitions could also help developers > > understanding what sort of IO that these use cases generate. > > True, but I think Adam has a point here. IIRC mmtests comes with some scripts > to download, build and run the desired applications and then do the maths. > > In this day and age people would probably want to use a container with the > application inside and some automation around it to run the benchmark and > present the results. Yeah, although containers also do have some impact on the benchmark behavior (not that much for IO but for scheduling and memory management it is more visible) so bare-metal testing is still worthwhile. Mmtests actually already have some support for VM testing and we have implemented basic container testing just recently. There are still rough edges and more work is needed but mmtests are also moving into the next decade ;). Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
