Skip to content

Application for HTTP benchmarking via different rules and configs


Notifications You must be signed in to change notification settings


Repository files navigation

Go Benchmark App

Build Status License codecov Coverage Status Go Report Card GoDoc

The efficiency and speed of application - our goal and the basic idea.

Go Benchmark App

Application for HTTP-benchmarking via different rules and configurations.

Configurations provided via TOML-config.

Our main aims - compare different web-applications that we want to compare with same benchmarks tools, same parameters, repeated and distributed in time. Get average results and compare it with other applications.

This will allow us to analyze and compare the performance bottlenecks, and to take appropriate measures. The efficiency and speed of application - our goal and the basic idea.

Benchmarks tools

ab, wrk, siege

It should be installed.

How to configure

All config at config/main.toml

# Title for describing benchmarks
title = "CMS benchmarks"
# Benchmarks version
version = "0.1"
# Delay via try in seconds
delay = 20
# How much we should try
try = 10

# ab benchmarks parametres
concurency = 5000
keepalive = false
requests = 10000

# wrk benchmarks parametres
connections = 5000
duration = 10
threads = 1000

# siege benchmarks parametres
concurrent = 100
time = 30

# Applications parametres - list
title = "Application Banchamrs Title"
path = "fool/path/to/app"
url = "http://localhost:5000/test"

How to use

  • Installed Go 1.6+

  • Check is benchmarks tools installed:

    $ whereis ab

    $ whereis wrk

    $ whereis siege

  • Configure config/main.toml in current dirrectory as mentioned before.

  • Install application: $ go install

  • Command-line help: $ go-benchmark-app -h

Go Benchmark Applications v1.0.0
  -c FILE
    	load configuration from FILE (default "config/main.toml")
  -v	verbose output
  • To change config file - run: $ go-benchmark-app -c path/to/cfg.toml
  • Verbose output: $ go-benchmark-app -v

Tips & Tricks

  • When your benchmarks test failed with socket error (more resources unawailable), try increase delay options at config file (for example 60 sec) or/and change system limits to opened files, TCP/IP configuration and other system limitations.
  • For flexibility running test applications you can create recipe for that. For example set at config file:
title = "My App"
path = "apps/"
url = "http://localhost:5000/test"

and apps/ file:

prepare -to -run
/full/path/to/app -v param -d param -etc

in that way you can run docker, nginx or another useful commands.

For one application we use one URL, because it's simplify results analyze, interpretation, comparison.

License: MIT License