| commit | 521ad54a3fe2d597b5b02c8c766cebb442434b8d | [log] [tgz] |
|---|---|---|
| author | Theodore Ts'o <tytso@mit.edu> | Fri Apr 17 23:06:50 2020 -0400 |
| committer | Theodore Ts'o <tytso@mit.edu> | Fri Apr 17 23:06:50 2020 -0400 |
| tree | aae78feb896829a5d8c5a5a616516c36277011d3 | |
| parent | a93380c74fd2932177274f697b667a0fb77e4626 [diff] |
test-appliance: update VM pricing table in gce-xfstests Add the e2 machine types since they are cheaper than the n1 machine types with roughly the same performance. The n2 machine types are more expensive per CPU hour, and is faster, and is a slight net win over the n1 machine types --- but the e2 VM's are better. Comparing the runtime and costs of: gce-xfstests -c ext4/4k -g auto --machtype <machtype> GCE MachType Time Cost Savings n1-standard-2 6178s 20.5 cents --- e2-standard-2 5942s 15.0 cents 26.8% n2-standard-2 5513s 18.6 cents 9.3% This patch doesn't actually enable the automatic selection of the e2 VM's, since we need to be careful; not all of the GCE zones support the e2 machine types. (All of the prices are for the us-central1 zone but it's really the relative differences in prices which are useful for selecitng the appropriate machine type.) Signed-off-by: Theodore Ts'o <tytso@mit.edu>
The xfstests-bld project was originally designed as system to make it easy to build xfstests in way that isolated it from the versions of various libraries such as libaio, xfsprogs, that were available in a particular distribution. It has since evolved to have four primary functions:
More details about how to use xfstests-bld to carry out these three functions can be found in the Documentation directory.
If you are first getting started using xfstests, you should probably read the Quickstart guide first. If you don't know much about xfstests, you may also want to read this introduction to xfstests.
The xfstests-bld project has been made available under the terms of the GNU General Public License, version 2. A copy can be found in the file named COPYING in the distribution.