If you're new to the project, welcome! Please feel free to ask questions here. We encourage new frameworks and contributors to ask questions. We're here to help!

This project provides representative performance measures across a wide field of web application frameworks. With much help from the community, coverage is quite broad and we are happy to broaden it further with contributions. The project presently includes frameworks on many languages including Go, Python, Java, Ruby, PHP, C#, Clojure, Groovy, Dart, JavaScript, Erlang, Haskell, Scala, Perl, Lua, C, and others. The current tests exercise plaintext responses, JSON seralization, database reads and writes via the object-relational mapper (ORM), collections, sorting, server-side templates, and XSS counter-measures. Future tests will exercise other components and greater computation.

Read more and see the results of our tests on cloud and physical hardware. For descriptions of the test types that we run, see the test requirements section.

If you find yourself in a directory or file that you're not sure what the purpose is, checkout our file structure in our documenation, which will briefly explain the use of relevant directories and files.

To get started developing you'll need to install docker or see our Quick Start Guide using vagrant

1. Clone TFB.

    $ git clone https://github.com/TechEmpower/FrameworkBenchmarks.git
   

2. Create the TFB Docker virtual network

    $ docker network create tfb
   

3. Run a test.

    $ docker run -it --network=tfb -v /var/run/docker.sock:/var/run/docker.sock --mount type=bind,source=[ABS PATH TO THIS DIR],target=/FrameworkBenchmarks techempower/tfb --mode verify --test gemini
   

That run script is pretty wordy, but each and every flag is required. Unfortunately, because of the way that Docker runs processes, you cannot put this inside of a shell script without breaking how ctrl+c and SIGTERM work (the shell script would receive the signal, do nothing with the underlying python suite running, and exit, orphaning the toolset to continue running).

• -it tells docker to run this in 'interactive' mode and simulate a TTY, so that ctrl+c is propagated.
• --network=tfb tells the container to join the 'tfb' Docker virtual network
• -v specifies which Docker socket path to mount as a volume in the running container. This allows docker commands run inside this container to use the host container's docker to create/run/stop/remove containers.
• --mount mounts the FrameworkBenchmarks source directory as a volume to share with the container so that rebuilding the toolset image is unnecessary and any changes you make on the host system are available in the running toolset container.
• techempower/tfb is the name of toolset container to run
• --mode verify --test gemini are the command to pass to the toolset.

You may not want to call step 4 from above every time. You can add an alias to your ~/.bash_aliases file to shorten it since it will not change once configured:

$ alias tfb="docker run -it --network=tfb -v /var/run/docker.sock:/var/run/docker.sock --mount type=bind,source=[ABS PATH TO THIS DIR],target=/FrameworkBenchmarks techempower/tfb"

$ source ~/.bash_aliases

Now you can run the toolset via tfb:

$ tfb --mode verify --test gemini

• Docker expects Linux-style paths. If you cloned on your C:\ drive, then [ABS PATH TO THIS DIR] would be /c/FrameworkBenchmarks.
• Docker for Windows understands /var/run/docker.sock even though that is not a valid path on Windows. Docker Toolbox may not - use at your own risk.

Get started developing quickly by utilizing vagrant with TFB. Git, Virtualbox and vagrant are required.

1. Clone TFB.

    $ git clone https://github.com/TechEmpower/FrameworkBenchmarks.git
   

2. Change directories

    $ cd FrameworkBenchmarks/deployment/vagrant
   

3. Build the vagrant virtual machine

    $ vagrant up
   

4. Run a test

    $ vagrant ssh
    $ tfb --mode verify --test gemini
   

Once you open an SSH connection to your vagrant box, start the new test initialization wizard.

    vagrant@TFB-all:~/FrameworkBenchmarks$ tfb --new

This will walk you through the entire process of creating a new test to include in the suite.

Our official documentation can be found at frameworkbenchmarks.readthedocs.org. If you find any errors or areas for improvement within the docs, feel free to either submit a pull request or issue at the documentation repository.

Results of continuous benchmarking runs are available in real time here.

If you have a results.json file that you would like to visualize, you can do that here. You can also attach a runid parameter to that url where runid is a run listed on tfb-status like so: https://www.techempower.com/benchmarks/#section=test&runid=fd07b64e-47ce-411e-8b9b-b13368e988c6

The community has consistently helped in making these tests better, and we welcome any and all changes. Reviewing our contribution practices and guidelines will help to keep us all on the same page. The contribution guide can be found in the TFB documentation.

Join in the conversation on our mailing list, on Twitter, or chat with us on Freenode at #techempower-fwbm.