ping_pong(1)

ping_pong1

Measures the ping-pong byte range lock latency

Usage

ping_pong {-r | -w | -rw} [-m] [-c] FILENAME NUM-LOCKS

Overview

ping_pong measures the byte range lock latency. It is especially useful on a cluster of nodes sharing a common lock manager as it will give some indication of the lock manager's performance under stress.

FILENAME is a file on shared storage to use for byte range locking tests.

NUM-LOCKS is the number of byte range locks, so needs to be (strictly) greater than the number of nodes in the cluster.

Options

-r

test read performance

-w

test write performance

-m

use mmap

-c

validate the locks

Examples

Testing lock coherence

      ping_pong test.dat N

Testing lock coherence with lock validation

      ping_pong -c test.dat N

Testing IO coherence

      ping_pong -rw test.dat N

Releases

7 releases since Debian 7 (Wheezy); the text changed 6 times.

  1. 7
  2. 8
  3. 9
  4. 10
  5. 11
  6. 12
  7. 13

-c since Debian 8 (Jessie).

Author

This documentation was written by Mathieu Parent

From ctdb 2:4.22.11+dfsg-0+deb13u1 in Debian 13 (Trixie). Parsed by carta from the page's man source.