KVM-test: Add two scripts to disable services for perf tests
PATCH 1/1 KVM-test: Add two scripts to disable services for perf tests
System services on guest and host take uncertain resource, it effects the perf results. We can use the below two scripts to disable some services of host and guest.
stop_serivices_perf.sh is used to stop the running serivices. off_service_perf.sh is used to off services when host starts up.
We can use them to prepare environment for performance testcases.
--- client/tests/kvm/scripts/off_services_perf.sh | 27 ++++++++++++++++++++++++ client/tests/kvm/scripts/stop_services_perf.sh | 27 ++++++++++++++++++++++++ 2 files changed, 54 insertions(+), 0 deletions(-) create mode 100755 client/tests/kvm/scripts/off_services_perf.sh create mode 100755 client/tests/kvm/scripts/stop_services_perf.sh
client/tests/kvm/scripts/off_services_perf.sh new file +27 -0
@@ -0,0 +1,27 @@ +#!/bin/bash +chkconfig auditd off +chkconfig autofs off +chkconfig avahi-daemon off +chkconfig crond off +chkconfig cups off +chkconfig ip6tables off +chkconfig sendmail off +chkconfig smartd off +chkconfig xfs off +chkconfig acpid off +chkconfig atd off +chkconfig haldaemon off +chkconfig mdmonitor off +chkconfig netfs off +chkconfig rhnsd off +chkconfig rpcgssd off +chkconfig rpcidmapd off +chkconfig abrtd off +chkconfig kdump off +chkconfig koan off +chkconfig libvirt-guests off +chkconfig ntpdate off +chkconfig portreserve off +chkconfig postfix off +chkconfig rhsmcertd off +chkconfig tuned off
client/tests/kvm/scripts/stop_services_perf.sh new file +27 -0
@@ -0,0 +1,27 @@ +#!/bin/bash +service auditd stop +service avahi-daemon stop +service anacron stop +service qpidd stop +service smartd stop +service crond stop +service haldaemon stop +service opensmd stop +service openibd stop +service yum-updatesd stop +service collectd stop +service bluetooth stop +service cups stop +service cpuspeed stop +service hidd stop +service isdn stop +service kudzu stop +service lvm2-monitor stop +service mcstrans stop +service mdmonitor stop +service messagebus stop +service restorecond stop +service rhnsd stop +service rpcgssd stop +service setroubleshoot stop +service smartd stop
Quoted 8 lines · Amos Kong
System services on guest and host take uncertain resource, it effects
the perf results. We can use the below two scripts to disable some
services of host and guest.
Quoted 7 lines
stop_serivices_perf.shis used to stop the running serivices.
off_service_perf.shis used to off services when host starts up.We can use them to prepare environment for performance testcases.
Which environment? I assume this should secured by an Distribution
specific guard:
E.g.
if [ -f /etc/redhat-release ] then
----- Original Message -----
Quoted 8 lines
Quoted 5 lines · Amos Kong
System services on guest and host take uncertain resource, it effects
the perf results. We can use the below two scripts to disable some services of host and guest.
Quoted 7 lines
Quoted 4 lines
stop_serivices_perf.shis used to stop the running serivices.off_service_perf.shis used to off services when host starts up.We can use them to prepare environment for performance testcases.
Which environment? I assume this should secured by an Distribution specific guard:
prepare clean testing environment.
Quoted 3 lines
E.g.
if [ -f
/etc/redhat-release] then
yes.
Quoted 6 lines · Amos Kong
System services on guest and host take uncertain resource, it effects the perf results. We can use the below two scripts to disable some services of host and guest.
stop_serivices_perf.shis used to stop the running serivices.off_service_perf.shis used to off services when host starts up.
Hi Amos, thanks! I've been thinking about those scripts, let me summarize my thoughts:
* If we are going to make this using scripts, then we should try as
much as possible to be distro agnostic.
* We could detect services present on guest first before trying to
disable them, ie, instead of just issuing a service koan stop, verify if there's a /etc/init.d/koan first.
* Have you considered doing this env setup using shell commands typed
on an ssh session, such as
session = vm.wait_for_login()
session.cmd('service auditd stop')
Rather than a script? It's one less script to maintain under the scripts/ directory.
* Your approach is a blacklist of services that will be turned off.
What if we used a 'whitelist' approach and kept a list of the fundamental services needed and turn off *everything else*?
Please let me know what you think about this. I'm not applying this for now.
----- Original Message -----
Quoted 12 lines · Amos Kong
Quoted 7 lines
System services on guest and host take uncertain resource, it effects
the perf results. We can use the below two scripts to disable some services of host and guest.
stop_serivices_perf.shis used to stop the running serivices.off_service_perf.shis used to off services when host starts up.Hi Amos, thanks! I've been thinking about those scripts, let me summarize my thoughts:
Quoted 6 lines
* If we are going to make this using scripts, then we should try as
much as possible to be distro agnostic.* We could detect services present on guest first before trying to
disable them, ie, instead of just issuing a service koan stop, verify if there's a/etc/init.d/koanfirst.
We have a black list, if one server exist in the guest (/etc/init.d/*), then stop it.
Some services need to be disabled by 'chkconfig * off', we can execute a python/shell script in post installation, checking if service exists is also necessary.
Quoted 7 lines
* Have you considered doing this env setup using shell commands typed
on an ssh session, such assession =
vm.wait_for_login()
session.cmd('service auditd stop')
Quoted 6 lines
Rather than a script? It's one less script to maintain under the
scripts/directory.* Your approach is a blacklist of services that will be turned off.
What if we used a 'whitelist' approach and kept a list of the fundamental services needed and turn off *everything else*?
Blacklist is safe and better, the whitelist is difficult to maintain.
Quoted 7 lines
Please let me know what you think about this. I'm not applying this for now.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html