This is an example of what information workloads should ultimately express. This is not a comprehensive definition of what SAP HANA needs for functioning, just a few things I dug out from the web. But it contains various types of settings that might be useful for workloads. For example the hugepage size as that is not something which is definite, the optimal size varies on the workload. Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx> --- data/workload/example.com/sap-hana.xml.in | 29 +++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 data/workload/example.com/sap-hana.xml.in diff --git a/data/workload/example.com/sap-hana.xml.in b/data/workload/example.com/sap-hana.xml.in new file mode 100644 index 000000000000..afc1216d41b3 --- /dev/null +++ b/data/workload/example.com/sap-hana.xml.in @@ -0,0 +1,29 @@ +<libosinfo version="0.0.1"> +<!-- Licensed under the GNU General Public License version 2 or later. + See http://www.gnu.org/licenses/ for a copy of the license text --> + <workload id="http://example.com/sap-hana";> + <short-id>sap-hana</short-id> + <_name>SAP HANA</_name> + <derive-from id="http://example.com/high-perf"/> + </workload> + + <!-- + these are features, can be just feature strings, but I just went with putting them in a bit more structured manner + --> + <features> + <hugepages size="1" unit="G"/> + <nic>passthrough</nic> + <io>native</io> + <disk cache="none"/> + </features> + + <!-- + these are flags that are required for this workload to run the best, there + might be removal of flags as well, maybe + --> + <cpu> + <flag>invtsc</flag> + <flag>rdtscp</flag> + </cpu> + +</libosinfo> -- 2.19.1 _______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
