archive
/
mitogen
mirror of https://github.com/mitogen-hq/mitogen.git
1
0
Fork 0
Code Releases Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
docs-master
stable
master
pr683
0.2-release
pull-request-checklist
dmw
circleci-project-setup
new-serialization
gh-pages
redirect
issue531
issue510
issue260
issue72
wip-fakessh-exit-status
v0.2.10rc1
v0.3.0rc1
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
working-django
working
v0.2.0
v0.2.1
v0.2.10
v0.2.10-rc.0
v0.2.2
v0.3.0
v0.3.0-rc.0
v0.3.1
v0.3.10
v0.3.11
v0.3.12
v0.3.13
v0.3.14
v0.3.15
v0.3.16
v0.3.17
v0.3.18
v0.3.2
v0.3.3
v0.3.4
v0.3.5
v0.3.6
v0.3.7
v0.3.8
v0.3.9
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7e5b064139'
${ noResults }
mitogen/tests/ansible/bench/loop-100-tasks.yml

116 lines
2.8 KiB
YAML
Raw Normal View History Unescape Escape

tests: import 2 more simple benchmarks.
6 years ago
# Execute 'hostname' 100 times, using 100 individual tasks. Each task causes a
# new WorkerProcess to be forked, along with get_vars() calculation, and in the
# Mitogen extension, reestablishment of the UNIX socket connectionto the
# multiplexer process.
#
# It does not measure at least module dependency scanning (cached after first
# iteration).
#
# See also: loop-100-items.yml
#
tests: Use meaningful play names
2 years ago
- name: bench/loop-100-tasks.yml
hosts: all
tests: import 2 more simple benchmarks.
6 years ago
tasks:
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
- command: hostname
tests: Tag resource intensive tasks, to skip when strategy=linear The ansible_mitogen test suite takes over an hour when Ansible is not accelerated by Mitogen. This change aims to reduce that by skipping tests with a large number of iterations when the linear strategy is chosen. The tagged tests are intended to uncover Mitogen resource leaks. Since Mitogen is not invoked when strategy=linear, the slight reduction in test coverage is an acceptable trade off.
4 years ago
tags:
- resource_intensive