ceph/suites/rados/thrash/workloads/radosbench.yaml

overrides:
  ceph:
    conf:
      client.0:
        debug ms: 1
        debug objecter: 20
        debug rados: 20
tasks:
- full_sequential:
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
added debug messages for radosbench.yaml Signed-off-by: tamil <tamil.muthamizhan@inktank.com> 2014-07-22 23:15:19 +00:00			`overrides:`
			`ceph:`
			`conf:`
			`client.0:`
			`debug ms: 1`
			`debug objecter: 20`
			`debug rados: 20`
Add small cluster thrashing tasks Signed-off-by: Samuel Just <samuel.just@dreamhost.com> 2012-01-17 23:06:24 +00:00			`tasks:`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- full_sequential:`
			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
			`- radosbench:`
			`clients: [client.0]`
			`time: 150`