Metadata-Version: 1.1
Name: ssbench
Version: 0.2.13
Summary: SwiftStack Swift Benchmarking Suite
Home-page: http://github.com/SwiftStack/ssbench
Author: SwiftStack, Inc.
Author-email: darrell@swiftstack.com
License: Apache License (2.0)
Description: What Is This?
        =============
        
        `SwiftStack`_ Benchmark Suite (``ssbench``) is a flexible and scalable
        benchmarking tool for the `OpenStack Swift`_ object storage system.
        
        The ``ssbench-master run-scenario`` command will run benchmark "scenarios"
        against an
        OpenStack Swift cluster, utilizing one or more distributed ``ssbench-worker``
        processes, saving statistics about the run to a file.  The ``ssbench-master
        report-scenario`` command can then generate a
        report from the saved statstics.  By default, ``ssbench-master run-scenario``
        will generate a report to STDOUT immediately following a benchmark run in
        addition to saving the raw results to a file.
        
        Coordination between the ``ssbench-master`` and one or more ``ssbench-worker``
        processes is managed through a pair of `PyZMQ`_ sockets.  This
        allows ``ssbench-master`` to distribute the benchmark run across many, many
        client servers while still coordinating the entire run (each worker can be
        given a job referencing an object created by a different worker).
        
        .. _`PyZMQ`: http://zeromq.github.com/pyzmq/
        .. _`OpenStack Swift`: http://docs.openstack.org/developer/swift/
        .. _`SwiftStack`: http://swiftstack.com/
        
        
        Installation on Ubuntu
        ----------------------
        
        I apologize for this stupid dependency dance with Ubuntu (tested with **12.04
        LTS Precise**).  With the --noop benchmark, ``gevent-zeromq`` is about 25%
        faster than ``pyzmq`` 2.2.0.1's zmq.green module, so I consider the annoying
        ``gevent-zeromq`` dependency worth it.  The ``gevent-zeormq``
        Cython build doesn't work with Ubuntu 12.04's Python's distribute, and Cython
        has to be installed in a prior "pip" command to be recognized by
        ``gevent-zeromq``'s setup.py::
        
          $ sudo apt-get install -y python-dev python-pip 'g++' libzmq-dev libevent-dev
          $ sudo pip install --upgrade distribute
          $ sudo pip install Cython gevent pyzmq==2.2.0
          $ sudo pip install ssbench
        
        Installation on CentOS 6.3
        --------------------------
        
        Installation on CentOS 6.3 using its stock Python 2.6::
        
          $ sudo rpm -Uvh http://mirror.pnl.gov/epel/6/i386/epel-release-6-8.noarch.rpm
          $ sudo yum install -y gcc gcc-c++ python-setuptools python-devel libevent-devel python-pip zeromq3-devel
          $ sudo pip-python install --upgrade argparse distribute Cython gevent pyzmq==2.2.0
          $ sudo pip-python install gevent-zeromq
          $ sudo pip-python install ssbench
        
        Installation on OS X
        --------------------
        
        On the Mac, I recommend installing `Homebrew`_ and using that to install Python
        2.7 and `libevent`_.  I haven't tested a fresh install in a while, but I had far
        less problems with Cython and gevent-zeormq on OS X, probably because the
        `Homebrew`_ Python was newer than Ubuntu 12.04's?
        
        .. _`Homebrew`: http://mxcl.github.com/homebrew/
        
        Then you should be able to just ``pip install ssbench``.
        
        Gevent 1.0beta
        --------------
        
        I have not tested ``ssbench`` against
        `gevent 1.0rc2`_, but according to an old `gevent blog post`_, gevent v1.x will
        bundle `libev`_ and not require the installation of `libevent`_ or
        `libev_`.  If you try ``ssbench`` with `gevent 1.0rc2`_, please let me know if
        and how that works...
        
        .. _`gevent 1.0rc2`: https://github.com/SiteSupport/gevent/downloads
        .. _`gevent blog post`: http://blog.gevent.org/2011/04/28/libev-and-libevent/
        .. _`libev`: http://software.schmorp.de/pkg/libev.html
        .. _`libevent`: http://libevent.org/
        
        
        Scenarios
        ---------
        
        A "scenario" (sometimes called a "CRUD scenario") is a utf8-encoded JSON file
        defining a benchmark run.  Specifically, it defines:
        
        - A ``name`` for the scenario (an arbitrary string)
        - A ``sizes`` list of "object size" classes.  Each object size class has a
          ``name``, a ``size_min`` minimum object size, a ``size_max`` maximum object
          size (in bytes), and an
          optional ``crud_profile`` for just this size.  If ``crud_profile`` is not
          given for a size, the top-level ``crud_profile`` will be used.  The
          ``crud_profile`` here is just like the top-level one, an array of 4 numbers
          whose relative sizes determine the percent chance of a Create, Read, Update,
          or Delete operation.  Objects created or updated within an object size
          class will have a size (in bytes) chosen at random uniformly between the
          minimum and maximum sizes.
        - An ``initial_files`` dictionary of initial file-counts per size class.  Each
          size class can have zero or
          more objects uploaded *prior* to the benchmark run itself.  The proportion of
          initial files also defines the probability distribution of object sizes
          during the benchmark run itself.  So if a particular object size class is not
          included in ``initial_files`` or has a value of 0 in ``initial_files``, then
          no objects in that size class will be used during the benchmark run.
        - An ``operation_count`` of operations to perform during the benchmark run.
          An operation is
          either a CREATE, READ, UPDATE, or DELETE of an object.  This value may be
          overridden for any given run with the ``-o COUNT`` flag to ``ssbench-master
          run-scenario``.
        - A ``crud_profile`` which determines the distribution of each kind of operation.
          For instance, ``[3, 4, 2, 2]`` would mean 27% CREATE, 36% READ, 18% UPDATE,
          and 18% DELETE.
        - A ``user_count`` which determines the maxiumum client concurrency during the
          benchmark run.  The user is responsible for ensuring there are enough workers
          running to support the scenario's defined ``user_count``.  (Each
          ``ssbench-worker`` process uses `gevent`_ to achive very efficient
          concurrency for the benchmark client requests.)  This value may be overridden
          for any given run with the ``-u COUNT`` flag to ``ssbench-master
          run-scenario``.
        - A ``container_count`` which determines how many Swift containers are used for
          the benchmark run.  This key is optional in the scenario file and defaults to
          100.  This value may be overridden for any given run with the ``-c
          COUNT`` flag to ``ssbench-master run-scenario``.
        - A ``container_concurrency`` value which determines the level of client
          concurrency used by ``ssbench-master`` to create the benchmark containers.
          This value is optional and defaults to 10.
        
        For each operation of the benchmark run, a size category is first chosen based
        on the relative counts for each size category in the ``initial_files``
        dictionary.  This probability for each size category appears under the "% Ops"
        column in the report.  Then an operation type is chosen based on that size
        category's CRUD profile (which can be individually specified or may be
        inherited from the "top level" CRUD profile).
        
        If each size category has its own CRUD profile, then the overall CRUD profile
        of the benchmark run will be a weighted average between the values in the "%
        Ops" column and the CRUD profile of each size category.  This weighted average
        CRUD profile is included in the report on the "CRUD weighted average" line.
        
        .. _`gevent`: http://www.gevent.org/
        
        ``ssbench`` comes with a few canned scenarios, but users are encouraged to
        experiment and define their own.
        
        Here is an example JSON scenario file::
        
          {
            "name": "Small test scenario",
            "sizes": [{
              "name": "tiny",
              "size_min": 4096,
              "size_max": 65536
            }, {
              "name": "small",
              "size_min": 100000,
              "size_max": 200000
            }],
            "initial_files": {
              "tiny": 100,
              "small": 10
            },
            "operation_count": 500,
            "crud_profile": [3, 4, 2, 2],
            "user_count": 7
          }
        
        **Beware:** hand-editing JSON is error-prone.  Watch out for trailing
        commas, in particular.
        
        Usage
        -----
        
        The ``ssbench-worker`` script's usage message may be generated with::
        
          $ ssbench-worker -h
          usage: ssbench-worker [-h] [--zmq-host ZMQ_HOST]
                                [--zmq-work-port ZMQ_WORK_PORT]
                                [--zmq-results-port ZMQ_RESULTS_PORT] [-c CONCURRENCY]
                                [--retries RETRIES] [-p COUNT] [-v]
                                worker_id
        
          ...
        
        The ``ssbench-master`` command requires one sub-command, which is currently
        either ``run-scenario`` to actually run a benchmark scenario,
        ``report-scenario`` to report on an existing scenario result data file, or
        ``kill-workers`` to tell connected ``ssbench-worker`` processes not started
        with ``--workers`` to kill themselves::
        
          $ ssbench-master -h
          usage: ssbench-master [-h] [-v]
                                {kill-workers,run-scenario,report-scenario} ...
        
          Benchmark your Swift installation
        
          positional arguments:
            {kill-workers,run-scenario,report-scenario}
              kill-workers        Tell all workers to exit.
              run-scenario        Run CRUD scenario, saving statistics. You must supply
                                  a valid set of v1.0 or v2.0 auth credentials. See
                                  usage message for run-scenario for more details.
              report-scenario     Generate a report from saved scenario statistics
        
          optional arguments:
            -h, --help            show this help message and exit
            -v, --verbose         Enable more verbose output. (default: False)
        
            usage: ssbench-master [-h] [-v]
                                  {kill-workers,run-scenario,report-scenario} ...
        
            Benchmark your Swift installation
        
        The ``run-scenario`` sub-command of ``ssbench-master`` actually
        runs a benchmark scenario::
        
          $ ssbench-master run-scenario -h
          usage: ssbench-master run-scenario [-h] -f SCENARIO_FILE
                                             [--zmq-bind-ip BIND_IP]
                                             [--zmq-work-port PORT]
                                             [--zmq-results_port PORT] [-V AUTH_VERSION]
                                             [-A AUTH_URL] [-U USER] [-K KEY]
                                             [--os-username <auth-user-name>]
                                             [--os-password <auth-password>]
                                             [--os-tenant-id <auth-tenant-id>]
                                             [--os-tenant-name <auth-tenant-name>]
                                             [--os-auth-url <auth-url>]
                                             [--os-auth-token <auth-token>]
                                             [--os-storage-url <storage-url>]
                                             [--os-region-name <region-name>]
                                             [--os-service-type <service-type>]
                                             [--os-endpoint-type <endpoint-type>]
                                             [--os-cacert <ca-certificate>] [--insecure]
                                             [-S STORAGE_URL] [-T TOKEN] [-c COUNT]
                                             [-u COUNT] [-o COUNT] [--workers COUNT]
                                             [--batch-size COUNT] [-q] [--profile]
                                             [--noop] [-k]
                                             [--connect-timeout CONNECT_TIMEOUT]
                                             [--network-timeout NETWORK_TIMEOUT]
                                             [-s STATS_FILE] [-r] [--pctile PERCENTILE]
          ...
        
        
        The ``report-scenario`` sub-command of ``ssbench-master`` reports on a
        previously-run benchmark scenario::
        
          $ ssbench-master report-scenario -h
          usage: ssbench-master report-scenario [-h] -s STATS_FILE [-f REPORT_FILE]
                                                [--pctile PERCENTILE] [-r RPS_HISTOGRAM]
                                                [--profile]
        
          ...
        
        The ``kill-workers`` sub-command of ``ssbench-master`` kills all
        ``ssbench-worker`` processes which are pointed at the ``ssbench-master``
        ZMQ sockets (this is useful for multi-server benchmark runs where the workers
        were not started with ``ssbench-master``'s ``--workers`` option)::
        
          $ ssbench-master kill-workers -h
          usage: ssbench-master kill-workers [-h] [--zmq-bind-ip BIND_IP]
                                             [--zmq-work-port PORT]
                                             [--zmq-results_port PORT]
        
          ...
        
        Authentication
        --------------
        
        ``ssbench-master`` supports all the same authentication arguments, with similar
        semantics, as `python-swiftclient`_'s command-line tool, ``swift``.
        
        For v1.0 authentication, you just need ``ST_AUTH``, ``ST_USER``, and ``ST_KEY``
        defined in the environment or overridden/set on the command-line with ``-A``,
        ``-U``, and ``-K``, respectively.
        
        For v2.0 authentication (Keystone), it's more complicated and you should refer
        to Keystone and/or `python-swiftclient`_ documentation for more help.
        
        Regardless of which version of authentication is used, you may specify ``-S
        <storage_url>`` on the command-line to override the Storage URL returned from
        the authentication system.
        
        .. _`python-swiftclient`: https://github.com/openstack/python-swiftclient
        
        
        Example Multi-Server Run
        ------------------------
        
        Start one or more ``ssbench-worker`` processes on each server (each
        ``ssbench-worker`` process defaults to a maximum `gevent`_-based concurrency
        of 256, but the ``-c`` option can override that default).  Use the
        ``--zmq-host`` command-line parameter to specify the host on which you will run
        ``ssbench-master``.::
        
          bench-host-01$ ssbench-worker -c 1000 --zmq-host bench-host-01 1 &
          bench-host-01$ ssbench-worker -c 1000 --zmq-host bench-host-01 2 &
        
          bench-host-02$ ssbench-worker -c 1000 --zmq-host bench-host-01 3 &
          bench-host-02$ ssbench-worker -c 1000 --zmq-host bench-host-01 4 &
        
        Finally, run one ``ssbench-master`` process which will manage and coordinate
        the multi-server benchmark run::
        
          bench-host-01$ ssbench-master run-scenario -f scenarios/very_small.scenario -u 2000 -o 40000
        
        The above example would involve a total client concurrency of 2000, spread
        evenly among the four workers on two hosts (``bench-host-01`` and
        ``bench-host-02``).  The four workers, as started in the above example,
        could support a maximum total client concurrency (``-u`` option to
        ``ssbench-master``) up to 4000.
        
        
        Example Simple Single-Server Run
        --------------------------------
        
        If you only need workers running on the local host, you can do so with a single
        command.  Simply use the ``--workers COUNT`` option to ``ssbench-master``::
        
          $ ssbench-master run-scenario -f scenarios/very_small.scenario -u 4 -c 80 -o 613 --pctile 50 --workers 2
          INFO:root:Spawning local ssbench-worker (logging to /tmp/ssbench-worker-local-0.log) with ssbench-worker --zmq-host 127.0.0.1 --zmq-work-port 13579 --zmq-results-port 13580 --concurrency 2 0
          INFO:root:Spawning local ssbench-worker (logging to /tmp/ssbench-worker-local-1.log) with ssbench-worker --zmq-host 127.0.0.1 --zmq-work-port 13579 --zmq-results-port 13580 --concurrency 2 1
          INFO:root:Starting scenario run for "Small test scenario"
          INFO:root:Ensuring 80 containers (ssbench_*) exist; concurrency=10...
          INFO:root:Initializing cluster with stock data (up to 4 concurrent workers)
          INFO:root:Starting benchmark run (up to 4 concurrent workers)
          Benchmark Run:
            X    work job raised an exception
            .  <  1s first-byte-latency
            o  <  3s first-byte-latency
            O  < 10s first-byte-latency
            * >= 10s first-byte-latency
            _  <  1s last-byte-latency  (CREATE or UPDATE)
            |  <  3s last-byte-latency  (CREATE or UPDATE)
            ^  < 10s last-byte-latency  (CREATE or UPDATE)
            @ >= 10s last-byte-latency  (CREATE or UPDATE)
          .___..__..__.__..____._._._._.___.__.____..._._._.__._.._.____._.__._.__..._..
          .._.._..._..._........_._.._.___....__...._..._.__._.._._........_..._..__....
          .._..__.___.._._..__.._..._.___.___..._._____.__....___.._._..__.......___._._
          .__.._.___.._.___._._._._.._.__.________._.........__..__._._.._._.__._.___._.
          ._._...._._.._..._.._...______..._____.__.._....._...._._.____.._._._.___.._._
          .._._.___...___.._....._.__..__.......__._...__.__...__.._._...__._..._.....__
          __..___._.__..__..___._.._._____...___.__..___._..._.____._._._....__...__..__
          ______.__.._....__..._.___.._._____...___.__..___.._._._______.____
          INFO:root:Deleting population objects from cluster
          INFO:root:Calculating statistics for 613 result items...
        
          Small test scenario
          Worker count:   2   Concurrency:   4  Ran 2013-02-20 17:10:18 UTC to 2013-02-20 17:10:26 UTC (7s)
        
          % Ops    C   R   U   D       Size Range       Size Name
           91%   % 27  36  18  18        4 kB -  66 kB  tiny
            9%   % 27  36  18  18      100 kB - 200 kB  small
          ---------------------------------------------------------------------
                   27  36  18  18      CRUD weighted average
        
          TOTAL
                 Count:   613  Average requests per second:  79.8
                                      min       max      avg      std_dev  50%-ile                   Worst latency TX ID
                 First-byte latency:  0.004 -   0.079    0.019  (  0.014)    0.015  (all obj sizes)  tx684b3b058d52403fbda528ffaec66a5f
                 Last-byte  latency:  0.004 -   0.167    0.043  (  0.027)    0.040  (all obj sizes)  txbd735d5cde494a9ab4ed0a961dd7c0b5
                 First-byte latency:  0.004 -   0.079    0.019  (  0.013)    0.014  (    tiny objs)  tx684b3b058d52403fbda528ffaec66a5f
                 Last-byte  latency:  0.004 -   0.167    0.042  (  0.027)    0.038  (    tiny objs)  txbd735d5cde494a9ab4ed0a961dd7c0b5
                 First-byte latency:  0.009 -   0.049    0.025  (  0.013)    0.024  (   small objs)  txc9479d86f4bb4606bfcdb96f55ff2127
                 Last-byte  latency:  0.019 -   0.123    0.054  (  0.026)    0.048  (   small objs)  tx3b2d5943869a4d65af887ef00d95271a
        
          CREATE
                 Count:   179  Average requests per second:  23.3
                                      min       max      avg      std_dev  50%-ile                   Worst latency TX ID
                 First-byte latency:  N/A   -   N/A      N/A    (  N/A  )    N/A    (all obj sizes)
                 Last-byte  latency:  0.018 -   0.167    0.066  (  0.021)    0.066  (all obj sizes)  txbd735d5cde494a9ab4ed0a961dd7c0b5
                 First-byte latency:  N/A   -   N/A      N/A    (  N/A  )    N/A    (    tiny objs)
                 Last-byte  latency:  0.018 -   0.167    0.065  (  0.021)    0.066  (    tiny objs)  txbd735d5cde494a9ab4ed0a961dd7c0b5
                 First-byte latency:  N/A   -   N/A      N/A    (  N/A  )    N/A    (   small objs)
                 Last-byte  latency:  0.048 -   0.123    0.077  (  0.020)    0.078  (   small objs)  tx3b2d5943869a4d65af887ef00d95271a
        
          READ
                 Count:   215  Average requests per second:  28.3
                                      min       max      avg      std_dev  50%-ile                   Worst latency TX ID
                 First-byte latency:  0.004 -   0.032    0.012  (  0.006)    0.011  (all obj sizes)  tx9f4c63b2c7db4be5bca77dff8916cc7c
                 Last-byte  latency:  0.004 -   0.053    0.016  (  0.009)    0.014  (all obj sizes)  txc9c3813c1e494b67954fa0eb61b79a03
                 First-byte latency:  0.004 -   0.032    0.012  (  0.006)    0.011  (    tiny objs)  tx9f4c63b2c7db4be5bca77dff8916cc7c
                 Last-byte  latency:  0.004 -   0.042    0.015  (  0.007)    0.014  (    tiny objs)  txdd64a85dcbab4ddea1a9981be2db3430
                 First-byte latency:  0.009 -   0.027    0.015  (  0.006)    0.012  (   small objs)  txc9c3813c1e494b67954fa0eb61b79a03
                 Last-byte  latency:  0.019 -   0.053    0.033  (  0.011)    0.031  (   small objs)  txc9c3813c1e494b67954fa0eb61b79a03
        
          UPDATE
                 Count:   119  Average requests per second:  15.8
                                      min       max      avg      std_dev  50%-ile                   Worst latency TX ID
                 First-byte latency:  N/A   -   N/A      N/A    (  N/A  )    N/A    (all obj sizes)
                 Last-byte  latency:  0.023 -   0.108    0.064  (  0.019)    0.067  (all obj sizes)  tx5bf7d7107973419ea42e6ac0b1971cac
                 First-byte latency:  N/A   -   N/A      N/A    (  N/A  )    N/A    (    tiny objs)
                 Last-byte  latency:  0.023 -   0.108    0.063  (  0.019)    0.065  (    tiny objs)  tx5bf7d7107973419ea42e6ac0b1971cac
                 First-byte latency:  N/A   -   N/A      N/A    (  N/A  )    N/A    (   small objs)
                 Last-byte  latency:  0.052 -   0.102    0.077  (  0.017)    0.085  (   small objs)  tx7be6135fa8544e2d87c64b335e990e5d
        
          DELETE
                 Count:   100  Average requests per second:  13.7
                                      min       max      avg      std_dev  50%-ile                   Worst latency TX ID
                 First-byte latency:  0.010 -   0.079    0.035  (  0.012)    0.033  (all obj sizes)  tx684b3b058d52403fbda528ffaec66a5f
                 Last-byte  latency:  0.010 -   0.079    0.035  (  0.012)    0.033  (all obj sizes)  tx684b3b058d52403fbda528ffaec66a5f
                 First-byte latency:  0.010 -   0.079    0.035  (  0.013)    0.033  (    tiny objs)  tx684b3b058d52403fbda528ffaec66a5f
                 Last-byte  latency:  0.010 -   0.079    0.035  (  0.013)    0.033  (    tiny objs)  tx684b3b058d52403fbda528ffaec66a5f
                 First-byte latency:  0.020 -   0.049    0.036  (  0.009)    0.036  (   small objs)  txc9479d86f4bb4606bfcdb96f55ff2127
                 Last-byte  latency:  0.020 -   0.049    0.036  (  0.009)    0.036  (   small objs)  txc9479d86f4bb4606bfcdb96f55ff2127
        
          INFO:root:Scenario run results saved to /tmp/ssbench-results/Small_test_scenario.2013-02-20.091016.stat
          INFO:root:You may generate a report with:
            ssbench-master report-scenario -s /tmp/ssbench-results/Small_test_scenario.2013-02-20.091016.stat
        
        
        Scalability and Throughput
        --------------------------
        
        Assuming the Swift cluster being benchmarked is not the bottleneck, the
        scalability of ssbench may be increased by
        
        - Running up to one ``ssbench-worker`` process per CPU core on any number of
          benchmarking servers.
        - Increasing the default ``--batch-size`` parameter (defaults to 1) on both the
          ``ssbench-master`` and ``ssbench-worker`` command-lines.  Note that if you
          are running everything on one server and using the ``--workers`` argument to
          ``ssbench-master``, the ``--batch-size`` parameter passed to
          ``ssbench-master`` will be passed on to the automatically-started
          ``ssbench-worker`` processes.
        - For optimal scalability, the user-count (concurrency) should be greater than
          and also an even multiple of both the batch-size and number of
          ``ssbench-worker`` processes.
        
        As a simple example, on my quad-core MacBook Pro, I get around **9,800** requests
        per second with ``--noop`` (see below) with this command-line (a
        ``--batch-size`` of 1)::
        
          $ ssbench-master run-scenario ... -u 24 -o 30000 --workers 3 --noop
        
        But with a ``--batch-size`` of 8, I can get around **19,500** requests per second::
        
          $ ssbench-master run-scenario ... -u 24 -o 30000 --workers 3 --noop --batch-size 8
        
        
        HTTPS on OS X
        -------------
        
        When running ``ssbench-worker`` on a Mac, using HTTPS, I got a significant
        speed-up when setting ``OPENSSL_X509_TEA_DISABLE=1`` in the environment of my
        ``ssbench-worker`` processes.  I found this tip via a `curl blog post`_ after
        noticing a process named ``trustevaluationagent`` chewing up a lot of CPU
        during a benchmark run against a cluster using HTTPS.
        
        .. _`curl blog post`: http://daniel.haxx.se/blog/2011/11/05/apples-modified-ca-cert-handling-and-curl/
        
        The No-op Mode
        --------------
        
        To test the maximum throughput of the ``ssbench-master`` ==> ``beantalkd``
        ==> ``ssbench-worker`` infrastructure, you can add ``--noop`` to a
        ``ssbench-master run-scenario`` command and the scenario will be "run" but
        the ``ssbench-worker`` processes will not actually talk to the Swift cluster.
        
        In this manner, you may determine your maximum requests per second if talking
        to the Swift cluster were free.
        
        The reported "Average requests per second:" value in the "TOTAL" section of
        the report should be higher than you expect to get out of the Swift cluster
        itself.
        
        With an older version of ``ssbench`` which used a beanstalkd server to manage
        master/worker communication, my 2012 15" Retina Macbook Pro could get **~2,700
        requests per second** with ``--noop`` using a local beanstalkd, one
        ``ssbench-worker``, and a user count (concurrency) of 4.
        
        With ZeorMQ sockets (no beanstalkd involved), the same laptop can get between
        **7,000 and 8,000 requests per second** with ``--noop``.
        
        
        Contributing to ssbench
        -----------------------
        
        First, please use the Github Issues for the project when submitting bug reports
        or feature requests.
        
        Code submissions should be submitted as pull requests and all code should be
        PEP8 (v. 1.4.2) compliant.  Current unit test line coverage is not 100%, but
        code contributions should not *lower* the code coverage (so please include
        new tests or update existing ones as part of your change).  Running tests will
        probably require Python 2.7 and a few additional modules like ``flexmock`` and
        ``nose``.
        
        If contributing code which implements a feature or fixes
        a bug, please ensure a Github Issue exists prior to submitting the pull request
        and reference the Issue number in your commit message.
        
        When submitting your first pull request, please also update AUTHORS to include
        yourself, maintaining alphabetical ordering by last name.
        
        If any of the file(s) you change do not yet have a copyright line with your
        name, please add one at the bottom of the others, above the license text (but
        never remove any existing copyright lines).  Your copyright line should look
        something like::
        
          # Copyright (c) 2013 FirstName LastName
        
        
Keywords: openstack swift object storage benchmark
Platform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Information Technology
Classifier: Intended Audience :: System Administrators
Classifier: Intended Audience :: Telecommunications Industry
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Natural Language :: English
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python :: 2.7
Classifier: Topic :: Software Development :: Testing :: Traffic Generation
Classifier: Topic :: System :: Benchmark
Classifier: Topic :: Utilities
