Documentation overhaul

Vegeta's documentation today is OK, but it can be substantially improved. This issue is meant to track ideas and needs for better documentation.

examples/ directory

All common (or not so common) recipes and examples ought to be captured in an appropriately named file in the examples/ directory, be they CLI or library related.

The README should be reduc

I can't find any other explanation or formulas for results like median, average, min/max, req/sec in documentation, readme or web page. On the documentation page I tried basic scenario to search result/s and get no relevant page.

I found this question on stackoverflow, so I'm not only one who didn't understand it
https://stackoverflow.com/questions/39665250/locust-result-summary-how-to-underst

if you run

  const response = http.request("get", url);

you will either:

1. if http1 - get 400 (probably dependant on the implementation
2. if http2 - get WARN[0001] Request Failed error="get \"https://test-api.k6.io/\": stream error: stream ID 1; PROTOCOL_ERROR"

This is easily fixed by uppercasing get to GET 😄, but I would argue that we pro

背景是乐视大数据部接收机tcp协议接收机压力测试，服务端口为9999。采用falcon监控相关性能信息。
解决方式是tcpcopy服务器开启4倍流量时出现大量rst包现象，后来改为两个tcpcopy进程启动1倍流量后,恢复正常。看cpu参数我理解是单tcpcopy进程占用一个cpu核心100%，24核cpu没有完全使用。采用开启两个进程曲线救国。
10.116.95.87 target server

10.116.95.81 intercept
/usr/local/intercept/sbin/intercept -i eth1 -F 'tcp and

refer: microsoft/vscode#27950 (comment)

cc @kirksl

note that today you can do things like print foo in the debug terminal input / REPL as a workaround

背景描述

最近才开始了解项目，正在看文档，中文的文档在访问的时候会出现无法访问情况。简单查了一下服务好像不在国内

重点描述遇到的问题：在国内访问文档不稳定

期望的功能特性

期望 文档服务器在国内可以有镜像

I'm use docker image: direvius/yandex-tank latest a1099a214528
start it as in doc (with bash)
start check: yandex-tank-check-ssh -e yyyyy -u zzzzz

2019-03-10 15:30:03,949 INFO Execute on yyyyy: ls -l
....
2019-03-10 15:30:04,962 INFO Authentication (publickey) successful!
2019-03-10 15:30:05,464 INFO Output dat

I get the feeling that the Wiki doesn't really get read too much and is not as easy to find as the website. I'm going to suggest that we move all wiki content to the website and then close down the Wiki portion of the repo.

The website is using markdown with GitHub Pages so it should largely be a cut and paste job with some minor tweaking.

venv/lib/python3.7/site-packages/molotov/session.py:43
/mnt/c/Users/chartjes/normandy/venv/lib/python3.7/site-packages/molotov/session.py:43: DeprecationWarning: Inheritance class LoggedClientSession from ClientSession is discouraged
class LoggedClientSession(ClientSession):

contract-tests/test_api_v3.py::test_list
/mnt/c/Users/chartjes/normandy/venv/lib/python3.7/site-packages/aioht

The current docs on the main branch shows the following use:

var scenario = BuildScenario()
                .WithConcurrentCopies(1)
                .WithOutWarmUp()
                .WithDuration(TimeSpan.FromSeconds(2));

var allStats = NBomberRunner.RegisterScenarios(scenario).RunTest();
var stepStats = allStats.First(x => x.StepName == "simple step");

Assert.IsTrue(stepStats.Ok

Need a way to pass a token to be used with bearer authentication in requests

I think for very quickly looking at the output of your load test it would be cool if oha used some colors with sane defaults for how long something takes (maybe green 0s - 0.3s, orange, 0.3-0.8, red, >=0.8?).

I suggest using colors in the TUI view and in the final output. Of course, make it into an option but I think it should be "auto" by default so that if the terminal is detected to be capab

Also, it would be nice to change the long lines to multiline code blocks in order to remove a need of horizontal scrolling and provide an ability to compare different run methods.