#benchmark #benchmarks #performance #web-frameworks

Nate Brady 8022367e1c add current_benchmark.txt to .gitignore [ci skip] 8 năm trước cách đây
.github c3626d6da6 updated PR Template now that Round 13 is over 8 năm trước cách đây
deployment e9c5f6f782 DB Setup Changes / New Travis / Vagrant fix - The Promised Land! (#2417) 8 năm trước cách đây
frameworks 175b332cae fix Go/echo (#2450) 8 năm trước cách đây
toolset 28e311c6d0 Update H2O to version 2.1.0-beta4 (#2445) 8 năm trước cách đây
.gitignore 8022367e1c add current_benchmark.txt to .gitignore [ci skip] 8 năm trước cách đây
.mailmap 66235b61f7 Update mailmap 10 năm trước cách đây
.travis.yml 5d44d57cbb RevenJ framework testing fixes (#2442) 8 năm trước cách đây
LICENSE 8bc496bba6 Corrected third clause to remove unwanted "of the" 10 năm trước cách đây
README.md fb7d497c62 fix command line [ci skip] 8 năm trước cách đây
benchmark.cfg.example c5713b21be Merge pull request #2403 from TechEmpower/password-prompt-removal 8 năm trước cách đây

README.md

Welcome to TechEmpower Framework Benchmarks (TFB)

Build Status Documentation Status Issue Stats Issue Stats

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 Amazon EC2 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.

Quick Start Guide

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. Move into the vagrant-development directory.

    $ cd FrameworkBenchmarks/deployment/vagrant-development
    
  3. Turn on the VM (takes at least 20 minutes).

    $ vagrant up
    
  4. Enter the VM.

    $ vagrant ssh
    
  5. Move into the FrameworkBenchmarks directory in the vm.

    vagrant@TFB-all:~$ cd ~/FrameworkBenchmarks
    
  6. Run a test.

    vagrant@TFB-all:~/FrameworkBenchmarks$ ./toolset/run-tests.py --mode verify --test beego
    

Note: In order to run the same test again the results (located at FrameworkBenchmarks/results) directory needs to be removed prior to running the test again. This directory is automatically added when tests are run. You can do this automatically by adding the --clean option to the test command. --clean-all will remove the results and installs directories.

Official Documentation

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.

Contributing

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 at our Google Group, or chat with us on Freenode at #techempower-fwbm.