Giter Club home page Giter Club logo

vegeta's Introduction

Vegeta Build Status Go Report Card PkgGoDev Gitter Donate

Vegeta is a versatile HTTP load testing tool built out of a need to drill HTTP services with a constant request rate. It's over 9000!

Vegeta

Features

  • Usable as a command line tool and a Go library.
  • CLI designed with UNIX composability in mind.
  • Avoids nasty Coordinated Omission.
  • Extensive reporting functionality.
  • Simple to use for distributed load testing.
  • Easy to install and run (static binary, package managers, etc).

Install

Pre-compiled executables

Get them here.

macOS

You can install Vegeta using the Homebrew:

$ brew update && brew install vegeta

Or with MacPorts:

$ port install vegeta

Arch Linux

$ pacman -S vegeta

FreeBSD

On FreeBSD you can install Vegeta with the built in package manager because there is a Vegeta Package available.

$ pkg install vegeta

Source

git clone https://github.com/tsenart/vegeta
cd vegeta
make vegeta
mv vegeta ~/bin # Or elsewhere, up to you.

Versioning

Both the library and the CLI are versioned with SemVer v2.0.0.

After v8.0.0, the two components are versioned separately to better isolate breaking changes to each.

CLI releases are tagged with cli/vMAJOR.MINOR.PATCH and published on the GitHub releases page. As for the library, new versions are tagged with both lib/vMAJOR.MINOR.PATCH and vMAJOR.MINOR.PATCH. The latter tag is required for compatibility with go mod.

Contributing

See CONTRIBUTING.md.

Usage manual

Usage: vegeta [global flags] <command> [command flags]

global flags:
  -cpus int
    	Number of CPUs to use (default = number of cpus)
  -profile string
    	Enable profiling of [cpu, heap]
  -version
    	Print version and exit

attack command:
  -body string
    	Requests body file
  -cert string
    	TLS client PEM encoded certificate file
  -chunked
    	Send body with chunked transfer encoding
  -connections int
    	Max open idle connections per target host (default 10000)
  -dns-ttl value
    	Cache DNS lookups for the given duration [-1 = disabled, 0 = forever] (default 0s)
  -duration duration
    	Duration of the test [0 = forever]
  -format string
    	Targets format [http, json] (default "http")
  -h2c
    	Send HTTP/2 requests without TLS encryption
  -header value
    	Request header
  -http2
    	Send HTTP/2 requests when supported by the server (default true)
  -insecure
    	Ignore invalid server TLS certificates
  -keepalive
    	Use persistent connections (default true)
  -key string
    	TLS client PEM encoded private key file
  -laddr value
    	Local IP address (default 0.0.0.0)
  -lazy
    	Read targets lazily
  -max-body value
    	Maximum number of bytes to capture from response bodies. [-1 = no limit] (default -1)
  -max-connections int
    	Max connections per target host
  -max-workers uint
    	Maximum number of workers (default 18446744073709551615)
  -name string
    	Attack name
  -output string
    	Output file (default "stdout")
  -prometheus-addr string
    	Prometheus exporter listen address [empty = disabled]. Example: 0.0.0.0:8880
  -proxy-header value
    	Proxy CONNECT header
  -rate value
    	Number of requests per time unit [0 = infinity] (default 50/1s)
  -redirects int
    	Number of redirects to follow. -1 will not follow but marks as success (default 10)
  -resolvers value
    	List of addresses (ip:port) to use for DNS resolution. Disables use of local system DNS. (comma separated list)
  -root-certs value
    	TLS root certificate files (comma separated list)
  -session-tickets
    	Enable TLS session resumption using session tickets
  -targets string
    	Targets file (default "stdin")
  -timeout duration
    	Requests timeout (default 30s)
  -unix-socket string
    	Connect over a unix socket. This overrides the host address in target URLs
  -workers uint
    	Initial number of workers (default 10)

encode command:
  -output string
    	Output file (default "stdout")
  -to string
    	Output encoding [csv, gob, json] (default "json")

plot command:
  -output string
    	Output file (default "stdout")
  -threshold int
    	Threshold of data points above which series are downsampled. (default 4000)
  -title string
    	Title and header of the resulting HTML page (default "Vegeta Plot")

report command:
  -buckets string
    	Histogram buckets, e.g.: "[0,1ms,10ms]"
  -every duration
    	Report interval
  -output string
    	Output file (default "stdout")
  -type string
    	Report type to generate [text, json, hist[buckets], hdrplot] (default "text")

examples:
  echo "GET http://localhost/" | vegeta attack -duration=5s | tee results.bin | vegeta report
  vegeta report -type=json results.bin > metrics.json
  cat results.bin | vegeta plot > plot.html
  cat results.bin | vegeta report -type="hist[0,100ms,200ms,300ms]"

-cpus

Specifies the number of CPUs to be used internally. It defaults to the amount of CPUs available in the system.

-profile

Specifies which profiler to enable during execution. Both cpu and heap profiles are supported. It defaults to none.

-version

Prints the version and exits.

attack command

-body

Specifies the file whose content will be set as the body of every request unless overridden per attack target, see -targets.

-cert

Specifies the PEM encoded TLS client certificate file to be used with HTTPS requests. If -key isn't specified, it will be set to the value of this flag.

-chunked

Specifies whether to send request bodies with the chunked transfer encoding.

-connections

Specifies the maximum number of idle open connections per target host.

-dns-ttl

Specifies the duration to cache DNS lookups for. A zero value caches forever. A negative value disables caching altogether.

-max-connections

Specifies the maximum number of connections per target host.

-duration

Specifies the amount of time to issue request to the targets. The internal concurrency structure's setup has this value as a variable. The actual run time of the test can be longer than specified due to the responses delay. Use 0 for an infinite attack.

-format

Specifies the targets format to decode.

json format

The JSON format makes integration with programs that produce targets dynamically easier. Each target is one JSON object in its own line. The method and url fields are required. If present, the body field must be base64 encoded. The generated JSON Schema defines the format in detail.

jq -ncM '{method: "GET", url: "http://goku", body: "Punch!" | @base64, header: {"Content-Type": ["text/plain"]}}' |
  vegeta attack -format=json -rate=100 | vegeta encode
http format

The http format almost resembles the plain-text HTTP message format defined in RFC 2616 but it doesn't support in-line HTTP bodies, only references to files that are loaded and used as request bodies (as exemplified below).

Although targets in this format can be produced by other programs, it was originally meant to be used by people writing targets by hand for simple use cases.

Here are a few examples of valid targets files in the http format:

Simple targets
GET http://goku:9090/path/to/dragon?item=ball
GET http://user:password@goku:9090/path/to
HEAD http://goku:9090/path/to/success
Targets with custom headers
GET http://user:password@goku:9090/path/to
X-Account-ID: 8675309

DELETE http://goku:9090/path/to/remove
Confirmation-Token: 90215
Authorization: Token DEADBEEF
Targets with custom bodies
POST http://goku:9090/things
@/path/to/newthing.json

PATCH http://goku:9090/thing/71988591
@/path/to/thing-71988591.json
Targets with custom bodies and headers
POST http://goku:9090/things
X-Account-ID: 99
@/path/to/newthing.json
Add comments

Lines starting with # are ignored.

# get a dragon ball
GET http://goku:9090/path/to/dragon?item=ball
# specify a test account
X-Account-ID: 99

-h2c

Specifies that HTTP2 requests are to be sent over TCP without TLS encryption.

-header

Specifies a request header to be used in all targets defined, see -targets. You can specify as many as needed by repeating the flag.

-http2

Specifies whether to enable HTTP/2 requests to servers which support it.

-insecure

Specifies whether to ignore invalid server TLS certificates.

-keepalive

Specifies whether to reuse TCP connections between HTTP requests.

-key

Specifies the PEM encoded TLS client certificate private key file to be used with HTTPS requests.

-laddr

Specifies the local IP address to be used.

-lazy

Specifies whether to read the input targets lazily instead of eagerly. This allows streaming targets into the attack command and reduces memory footprint. The trade-off is one of added latency in each hit against the targets.

-max-body

Specifies the maximum number of bytes to capture from the body of each response. Remaining unread bytes will be fully read but discarded. Set to -1 for no limit. It knows how to interpret values like these:

  • "10 MB" -> 10MB
  • "10240 g" -> 10TB
  • "2000" -> 2000B
  • "1tB" -> 1TB
  • "5 peta" -> 5PB
  • "28 kilobytes" -> 28KB
  • "1 gigabyte" -> 1GB

-name

Specifies the name of the attack to be recorded in responses.

-output

Specifies the output file to which the binary results will be written to. Made to be piped to the report command input. Defaults to stdout.

-rate

Specifies the request rate per time unit to issue against the targets. The actual request rate can vary slightly due to things like garbage collection, but overall it should stay very close to the specified. If no time unit is provided, 1s is used.

A -rate of 0 or infinity means vegeta will send requests as fast as possible. Use together with -max-workers to model a fixed set of concurrent users sending requests serially (i.e. waiting for a response before sending the next request).

Setting -max-workers to a very high number while setting -rate=0 can result in vegeta consuming too many resources and crashing. Use with care.

-redirects

Specifies the max number of redirects followed on each request. The default is 10. When the value is -1, redirects are not followed but the response is marked as successful.

-resolvers

Specifies custom DNS resolver addresses to use for name resolution instead of the ones configured by the operating system. Works only on non Windows systems.

-root-certs

Specifies the trusted TLS root CAs certificate files as a comma separated list. If unspecified, the default system CAs certificates will be used.

-session-tickets

Specifies whether to support TLS session resumption using session tickets.

-targets

Specifies the file from which to read targets, defaulting to stdin. See the -format section to learn about the different target formats.

-timeout

Specifies the timeout for each request. A value of 0 disables timeouts.

-workers

Specifies the initial number of workers used in the attack. The actual number of workers will increase if necessary in order to sustain the requested rate, unless it'd go beyond -max-workers.

-max-workers

Specifies the maximum number of workers used in the attack. It can be used to control the concurrency level used by an attack.

report command

Usage: vegeta report [options] [<file>...]

Outputs a report of attack results.

Arguments:
  <file>  A file with vegeta attack results encoded with one of
          the supported encodings (gob | json | csv) [default: stdin]

Options:
  --type    Which report type to generate (text | json | hist[buckets] | hdrplot).
            [default: text]

  --buckets Histogram buckets, e.g.: '[0,1ms,10ms]'

  --every   Write the report to --output at every given interval (e.g 100ms)
            The default of 0 means the report will only be written after
            all results have been processed. [default: 0]

  --output  Output file [default: stdout]

Examples:
  echo "GET http://:80" | vegeta attack -rate=10/s > results.gob
  echo "GET http://:80" | vegeta attack -rate=100/s | vegeta encode > results.json
  vegeta report results.*

report -type=text

Requests      [total, rate, throughput] 1200, 120.00, 65.87
Duration      [total, attack, wait]     10.094965987s, 9.949883921s, 145.082066ms
Latencies     [min, mean, 50, 95, 99, max]  90.438129ms, 113.172398ms, 108.272568ms, 140.18235ms, 247.771566ms, 264.815246ms
Bytes In      [total, mean]             3714690, 3095.57
Bytes Out     [total, mean]             0, 0.00
Success       [ratio]                   55.42%
Status Codes  [code:count]              0:535  200:665
Error Set:
Get http://localhost:6060: dial tcp 127.0.0.1:6060: connection refused
Get http://localhost:6060: read tcp 127.0.0.1:6060: connection reset by peer
Get http://localhost:6060: dial tcp 127.0.0.1:6060: connection reset by peer
Get http://localhost:6060: write tcp 127.0.0.1:6060: broken pipe
Get http://localhost:6060: net/http: transport closed before response was received
Get http://localhost:6060: http: can't write HTTP request on broken connection

The Requests row shows:

  • The total number of issued requests.
  • The real request rate sustained during the attack period.
  • The throughput of successful requests over the total period.

The Duration row shows:

  • The attack time taken issuing all requests (total - wait)
  • The wait time waiting for the response to the last issued request (total - attack)
  • The total time taken in the attack (attack + wait)

Latency is the amount of time taken for a response to a request to be read (including the -max-body bytes from the response body).

  • min is the minimum latency of all requests in an attack.
  • mean is the arithmetic mean / average of the latencies of all requests in an attack.
  • 50, 90, 95, 99 are the 50th, 90th, 95th and 99th percentiles, respectively, of the latencies of all requests in an attack. To understand more about why these are useful, I recommend this article from @tylertreat.
  • max is the maximum latency of all requests in an attack.

The Bytes In and Bytes Out rows shows:

  • The total number of bytes sent (out) or received (in) with the request or response bodies.
  • The mean number of bytes sent (out) or received (in) with the request or response bodies.

The Success ratio shows the percentage of requests whose responses didn't error and had status codes between 200 and 400 (non-inclusive).

The Status Codes row shows a histogram of status codes. 0 status codes mean a request failed to be sent.

The Error Set shows a unique set of errors returned by all issued requests. These include requests that got non-successful response status code.

report -type=json

All duration like fields are in nanoseconds.

{
  "latencies": {
    "total": 237119463,
    "mean": 2371194,
    "50th": 2854306,
    "90th": 3228223,
    "95th": 3478629,
    "99th": 3530000,
    "max": 3660505,
    "min": 1949582
  },
  "buckets": {
    "0": 9952,
    "1000000": 40,
    "2000000": 6,
    "3000000": 0,
    "4000000": 0,
    "5000000": 2
  },
  "bytes_in": {
    "total": 606700,
    "mean": 6067
  },
  "bytes_out": {
    "total": 0,
    "mean": 0
  },
  "earliest": "2015-09-19T14:45:50.645818631+02:00",
  "latest": "2015-09-19T14:45:51.635818575+02:00",
  "end": "2015-09-19T14:45:51.639325797+02:00",
  "duration": 989999944,
  "wait": 3507222,
  "requests": 100,
  "rate": 101.01010672380401,
  "throughput": 101.00012489812,
  "success": 1,
  "status_codes": {
    "200": 100
  },
  "errors": []
}

In the buckets field, each key is a nanosecond value representing the lower bound of a bucket. The upper bound is implied by the next higher bucket. Upper bounds are non-inclusive. The highest bucket is the overflow bucket; it has no upper bound. The values are counts of how many requests fell into that particular bucket. If the -buckets parameter is not present, the buckets field is omitted.

report -type=hist

Computes and prints a text based histogram for the given buckets. Each bucket upper bound is non-inclusive.

cat results.bin | vegeta report -type='hist[0,2ms,4ms,6ms]'
Bucket         #     %       Histogram
[0,     2ms]   6007  32.65%  ########################
[2ms,   4ms]   5505  29.92%  ######################
[4ms,   6ms]   2117  11.51%  ########
[6ms,   +Inf]  4771  25.93%  ###################

report -type=hdrplot

Writes out results in a format plottable by https://hdrhistogram.github.io/HdrHistogram/plotFiles.html.

Value(ms)  Percentile  TotalCount  1/(1-Percentile)
0.076715   0.000000    0           1.000000
0.439370   0.100000    200         1.111111
0.480836   0.200000    400         1.250000
0.495559   0.300000    599         1.428571
0.505101   0.400000    799         1.666667
0.513059   0.500000    999         2.000000
0.516664   0.550000    1099        2.222222
0.520455   0.600000    1199        2.500000
0.525008   0.650000    1299        2.857143
0.530174   0.700000    1399        3.333333
0.534891   0.750000    1499        4.000000
0.537572   0.775000    1548        4.444444
0.540340   0.800000    1598        5.000000
0.543763   0.825000    1648        5.714286
0.547164   0.850000    1698        6.666667
0.551432   0.875000    1748        8.000000
0.553444   0.887500    1773        8.888889
0.555774   0.900000    1798        10.000000
0.558454   0.912500    1823        11.428571
0.562123   0.925000    1848        13.333333
0.565563   0.937500    1873        16.000000
0.567831   0.943750    1886        17.777778
0.570617   0.950000    1898        20.000000
0.574522   0.956250    1911        22.857143
0.579046   0.962500    1923        26.666667
0.584426   0.968750    1936        32.000000
0.586695   0.971875    1942        35.555556
0.590451   0.975000    1948        40.000000
0.597543   0.978125    1954        45.714286
0.605637   0.981250    1961        53.333333
0.613564   0.984375    1967        64.000000
0.620393   0.985938    1970        71.113640
0.629121   0.987500    1973        80.000000
0.638060   0.989062    1976        91.424392
0.648085   0.990625    1979        106.666667
0.659689   0.992188    1982        128.008193
0.665870   0.992969    1984        142.227279
0.672985   0.993750    1986        160.000000
0.680101   0.994531    1987        182.848784
0.687810   0.995313    1989        213.356091
0.695729   0.996094    1990        256.016385
0.730641   0.996484    1991        284.414107
0.785516   0.996875    1992        320.000000
0.840392   0.997266    1993        365.764448
1.009646   0.997656    1993        426.621160
1.347020   0.998047    1994        512.032770
1.515276   0.998242    1994        568.828214
1.683532   0.998437    1995        639.795266
1.887487   0.998633    1995        731.528895
2.106249   0.998828    1996        853.242321
2.325011   0.999023    1996        1023.541453
2.434952   0.999121    1996        1137.656428
2.544894   0.999219    1996        1280.409731
2.589510   0.999316    1997        1461.988304
2.605192   0.999414    1997        1706.484642
2.620873   0.999512    1997        2049.180328
2.628713   0.999561    1997        2277.904328
2.636394   0.999609    1997        2557.544757
2.644234   0.999658    1997        2923.976608
2.652075   0.999707    1997        3412.969283
2.658916   0.999756    1998        4098.360656
2.658916   0.999780    1998        4545.454545
2.658916   0.999805    1998        5128.205128
2.658916   0.999829    1998        5847.953216
2.658916   0.999854    1998        6849.315068
2.658916   0.999878    1998        8196.721311
2.658916   0.999890    1998        9090.909091
2.658916   0.999902    1998        10204.081633
2.658916   0.999915    1998        11764.705882
2.658916   0.999927    1998        13698.630137
2.658916   0.999939    1998        16393.442623
2.658916   0.999945    1998        18181.818182
2.658916   0.999951    1998        20408.163265
2.658916   0.999957    1998        23255.813953
2.658916   0.999963    1998        27027.027027
2.658916   0.999969    1998        32258.064516
2.658916   0.999973    1998        37037.037037
2.658916   0.999976    1998        41666.666667
2.658916   0.999979    1998        47619.047619
2.658916   0.999982    1998        55555.555556
2.658916   0.999985    1998        66666.666667
2.658916   0.999986    1998        71428.571429
2.658916   0.999988    1998        83333.333333
2.658916   0.999989    1998        90909.090909
2.658916   0.999991    1998        111111.111111
2.658916   0.999992    1998        125000.000000
2.658916   0.999993    1998        142857.142858
2.658916   0.999994    1998        166666.666668
2.658916   0.999995    1998        199999.999999
2.658916   0.999996    1998        250000.000000
2.658916   0.999997    1998        333333.333336
2.658916   0.999998    1998        500000.000013
2.658916   0.999999    1998        999999.999971
2.658916   1.000000    1998        10000000.000000

encode command

Usage: vegeta encode [options] [<file>...]

Encodes vegeta attack results from one encoding to another.
The supported encodings are Gob (binary), CSV and JSON.
Each input file may have a different encoding which is detected
automatically.

The CSV encoder doesn't write a header. The columns written by it are:

  1. Unix timestamp in nanoseconds since epoch
  2. HTTP status code
  3. Request latency in nanoseconds
  4. Bytes out
  5. Bytes in
  6. Error
  7. Base64 encoded response body
  8. Attack name
  9. Sequence number of request
  10. Method
  11. URL
  12. Base64 encoded response headers

Arguments:
  <file>  A file with vegeta attack results encoded with one of
          the supported encodings (gob | json | csv) [default: stdin]

Options:
  --to      Output encoding (gob | json | csv) [default: json]
  --output  Output file [default: stdout]

Examples:
  echo "GET http://:80" | vegeta attack -rate=1/s > results.gob
  cat results.gob | vegeta encode | jq -c 'del(.body)' | vegeta encode -to gob

plot command

Plot

Usage: vegeta plot [options] [<file>...]

Outputs an HTML time series plot of request latencies over time.
The X axis represents elapsed time in seconds from the beginning
of the earliest attack in all input files. The Y axis represents
request latency in milliseconds.

Click and drag to select a region to zoom into. Double click to zoom out.
Choose a different number on the bottom left corner input field
to change the moving average window size (in data points).

Arguments:
  <file>  A file output by running vegeta attack [default: stdin]

Options:
  --title      Title and header of the resulting HTML page.
               [default: Vegeta Plot]
  --threshold  Threshold of data points to downsample series to.
               Series with less than --threshold number of data
               points are not downsampled. [default: 4000]

Examples:
  echo "GET http://:80" | vegeta attack -name=50qps -rate=50 -duration=5s > results.50qps.bin
  cat results.50qps.bin | vegeta plot > plot.50qps.html
  echo "GET http://:80" | vegeta attack -name=100qps -rate=100 -duration=5s > results.100qps.bin
  vegeta plot results.50qps.bin results.100qps.bin > plot.html

Usage: Generated targets

Apart from accepting a static list of targets, Vegeta can be used together with another program that generates them in a streaming fashion. Here's an example of that using the jq utility that generates targets with an incrementing id in their body.

jq -ncM 'while(true; .+1) | {method: "POST", url: "http://:6060", body: {id: .} | @base64 }' | \
  vegeta attack -rate=50/s -lazy -format=json -duration=30s | \
  tee results.bin | \
  vegeta report

Usage: Distributed attacks

Whenever your load test can't be conducted due to Vegeta hitting machine limits such as open files, memory, CPU or network bandwidth, it's a good idea to use Vegeta in a distributed manner.

In a hypothetical scenario where the desired attack rate is 60k requests per second, let's assume we have 3 machines with vegeta installed.

Make sure open file descriptor and process limits are set to a high number for your user on each machine using the ulimit command.

We're ready to start the attack. All we need to do is to divide the intended rate by the number of machines, and use that number on each attack. Here we'll use pdsh for orchestration.

$ PDSH_RCMD_TYPE=ssh pdsh -b -w '10.0.1.1,10.0.2.1,10.0.3.1' \
    'echo "GET http://target/" | vegeta attack -rate=20000 -duration=60s > result.bin'

After the previous command finishes, we can gather the result files to use on our report.

$ for machine in 10.0.1.1 10.0.2.1 10.0.3.1; do
    scp $machine:~/result.bin $machine.bin &
  done

The report command accepts multiple result files. It'll read and sort them by timestamp before generating reports.

vegeta report *.bin

Another way to gather results in distributed tests is to use the built-in Prometheus Exporter and configure a Prometheus Server to get test results from all Vegeta instances. See attack option "prometheus-addr" for more details and a complete example in the section "Prometheus Support".

Usage: Real-time Analysis

If you are a happy user of iTerm, you can integrate vegeta with jplot using jaggr to plot a vegeta report in real-time in the comfort of your terminal:

echo 'GET http://localhost:8080' | \
    vegeta attack -rate 5000 -duration 10m | vegeta encode | \
    jaggr @count=rps \
          hist\[100,200,300,400,500\]:code \
          p25,p50,p95:latency \
          sum:bytes_in \
          sum:bytes_out | \
    jplot rps+code.hist.100+code.hist.200+code.hist.300+code.hist.400+code.hist.500 \
          latency.p95+latency.p50+latency.p25 \
          bytes_in.sum+bytes_out.sum

Usage: Library

The library versioning follows SemVer v2.0.0. Since lib/v9.0.0, the library and cli are versioned separately to better isolate breaking changes to each component.

See Versioning for more details on git tag naming schemes and compatibility with go mod.

package main

import (
  "fmt"
  "time"

  vegeta "github.com/tsenart/vegeta/v12/lib"
)

func main() {
  rate := vegeta.Rate{Freq: 100, Per: time.Second}
  duration := 4 * time.Second
  targeter := vegeta.NewStaticTargeter(vegeta.Target{
    Method: "GET",
    URL:    "http://localhost:9100/",
  })
  attacker := vegeta.NewAttacker()

  var metrics vegeta.Metrics
  for res := range attacker.Attack(targeter, rate, duration, "Big Bang!") {
    metrics.Add(res)
  }
  metrics.Close()

  fmt.Printf("99th percentile: %s\n", metrics.Latencies.P99)
}

Limitations

There will be an upper bound of the supported rate which varies on the machine being used. You could be CPU bound (unlikely), memory bound (more likely) or have system resource limits being reached which ought to be tuned for the process execution. The important limits for us are file descriptors and processes. On a UNIX system you can get and set the current soft-limit values for a user.

$ ulimit -n # file descriptors
2560
$ ulimit -u # processes / threads
709

Just pass a new number as the argument to change it.

Prometheus support

Vegeta has a built-in Prometheus Exporter that may be enabled during attacks so that you can point any Prometheus instance to Vegeta attack processes and monitor attack metrics.

To enable the Prometheus Exporter on the command line, set the "prometheus-addr" flag.

A Prometheus HTTP endpoint will be available only during the lifespan of an attack and will be closed right after the attack is finished.

The following metrics are exposed:

  • request_bytes_in - bytes count received from targeted servers by "url", "method" and "status"
  • request_bytes_out - bytes count sent to targeted server by "url", "method" and "status"
  • request_seconds - histogram with request latency and counters by "url", "method" and "status"
  • request_fail_count - count of failed requests by "url", "method", "status" and "message"

Check file lib/prom/grafana.json with the source of this sample dashboard in Grafana.

Limitations

  1. Prometheus scrapes metrics from a running vegeta attack process and assigns timestamps to samples on its server. This means result timestamps aren't accurate (i.e. they're scraping time, not result time).
  2. Configuring Prometheus to scrape vegeta needs to happen out-of-band. That's a hassle!
  3. Since there's no coordination between a vegeta attack process and a Prometheus server, an attack process will finish before Prometheus has the chance to scrape the latest observations.

Why aren't we using pushgateway instead? See this comment.

There's an issue tracking the proper solution to all these limitations which is a remote write integration.

License

See LICENSE.

Donate

If you use and love Vegeta, please consider sending some Satoshi to 1MDmKC51ve7Upxt75KoNM6x1qdXHFK6iW2. In case you want to be mentioned as a sponsor, let me know!

Donate Bitcoin

vegeta's People

Contributors

cwinters avatar dependabot[bot] avatar fxkr avatar geertjohan avatar gidsg avatar jpfuentes2 avatar mbodock avatar mickey avatar mistobaan avatar mstruebing avatar mxey avatar nathanejohnson avatar nh2 avatar nikai3d avatar nrekretep avatar olemchls avatar olleolleolle avatar oneness avatar peterbourgon avatar pgporada avatar proullon avatar pwaller avatar rs avatar salmaanp avatar sirupsen avatar slimsag avatar spier avatar tsenart avatar xla avatar zootalures avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vegeta's Issues

multiple sources

This tool is awesome and it has everything I need for the testing I do. I just need to be able to generate stateful traffic from multiple source addresses. Would it be possible to add a feature that will you to bind a /24 or arbitrary number of IP addresses and then split the traffic among these IP's on the same host? There is another project called curl-loader which is the only tool that I know that has this capability. It would be great if it is possible to add this feature to your tool. I see that you have documented a method to execute the tool on multiple hosts but I need to be able to use a /24 or more of address space.

thanks!

Report plot with status code detail

Do you think it is possible to plot a report where each status code is drawed in its own line?
For example let's say that I execute 200 request, 50 requests have HTTP 200, 150 have HTTP 500. I think it should be useful to have different lines in the output.

regards
Davide Icardi

report sometimes produces no output

Sometimes when I run report, it produces no output at all. However, if I run the exact same command a few more times, eventually the output is produced as expected. I not familiar with Go. Any idea what could be happening here?

Add disable-keepalive flag

The service I'm testing almost exclusively deals with short-lived, single request connections. With no option to disable keepalive I cannot run tests which properly simulate my production environment.

Would you accept a PR with a -disable-keepalive flag?

Packages

Create packages for:

  • Homebrew
  • Nixpkgs

duration 420m streams messages on STDOUT

using a duration higher then 420 starts displaying on STDOUT a stream of:

goroutine 114338 [select]:
^Created by github.com/tsenart/vegeta/lib.(*Attacker).Attack
        /Users/tomas/Code/go/src/github.com/tsenart/vegeta/lib/attack.go:154 +0x382

is it just a warning? I did not go trough running the app. Having 240 doesn't cause that stream.

Feature request: more robust plot output

Plotinum appears to have multiple runtime dependencies. It would be cool to reduce complexity there somehow, so I can confidently generate plots on remote machines or whatever.

Ability to save cookies

When using a series of targets, if a request sends a cookie in it's response, it would be super handy to have the option to save that cookie and use it in successive requests. I understand there are potential memory concerns there but in similar projects, it is a super handy option when simulating things like e-commerce transactions.

Ability to use output of previous attack for a new attack

Assuming I run an attack like this:

vegeta attack -duration=10s -rate=2 -targets=targets.txt > results.vr

It would be great if I could given results.vr to somebody and tell them to run it again like:

vegeta attack -playback=results.vr

This would then run the attack exactly the way that it was run the first time.

This assumes that all parameters used for the 1st attack could be persisted within results.vr somehow, including all URLs used. This would also be helpful in order to display the attack parameters in the different report forms, in order to distinguish different attacks from each other.

Ability to send a unique body for each target

Based on the documentation I don't see a way to presently do this. For example I would like to

GET /step/1/
POST key=val /step/1/
GET /step/2/
POST foo=bar /step/2/
...

It seems like this flow would be pretty common. The way I understand the documentation, any body I set will be sent to all targets. Am I misunderstanding that?

Unclear documentation of vegeta.NewAttacker

// NewAttacker returns a pointer to a new Attacker
//
// redirects is the max amount of redirects the attacker will follow.
// timeout is the client side timeout for each request.
// addr is the local IP address used for each request.
// If nil, a local IP address is automatically chosen.
func NewAttacker(redirects int, timeout time.Duration, laddr net.IPAddr) *Attacker {
  • the third parameter is called laddr
  • it's not possible to pass nil

invalid URLs are reported as 505 HTTP Version Not Supported

I had a few malformed URLs containing markup left from a crawling an HTML page. This is definitely user mistake but vegeta was reporting those as 505 (505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.)

What do you think about flag and ignore invalid URLs?

Example URL causing problem:

GET valid_url" class="accordion-toggle-sub"

Feature request: fixed size plots

A plot could be constrained to a fixed size, and data points scaled to fit.

Down/upsampling may be required. (I've heard that the maximum number of human-understandable data points in a single graph is 400.)

Support Websockets

Drones with embedded web servers typically use websockets. Shouldn't the prince of the Saiyans be able to attack enemies in the air?

Output requests that are over a configurable threshold

It is nice to get all errors logged in vegeta report.

For many use cases a requests that takes longer than a certain threshold is almost as bad as a call that throws a server error or times out.

Therefore it would be useful to be able to pass a threshold to vegeta like:
vegeta attack -threshold=2s ... | vegeta report

All requests that take longer than that request should then be listed like this:

Error Set:
<all URLs with some HTTP error>
Above Threshold Set (2s):
<all URLs above 2s threshold>

One could also add a horizontal line for the threshold in the output of vegeta report -reporter=plot.

Is this a good idea? And is this doable?
I don't know go much but I am happy to help on this.

out of memory with big big input file

fatal error: runtime: out of memory

goroutine 16 [running]:
runtime.throw(0x890077)
/usr/src/go/src/pkg/runtime/panic.c:520 +0x69 fp=0x7f1595b636d8 sp=0x7f1595b636c0
runtime.SysMap(0xc2dee20000, 0x1c040000, 0x574f00, 0x89b998)
/usr/src/go/src/pkg/runtime/mem_linux.c:147 +0x93 fp=0x7f1595b63708 sp=0x7f1595b636d8
runtime.MHeap_SysAlloc(0x8a7980, 0x1c040000)
/usr/src/go/src/pkg/runtime/malloc.goc:616 +0x15b fp=0x7f1595b63760 sp=0x7f1595b63708
MHeap_Grow(0x8a7980, 0xe020)
/usr/src/go/src/pkg/runtime/mheap.c:319 +0x5d fp=0x7f1595b637a0 sp=0x7f1595b63760
MHeap_AllocLocked(0x8a7980, 0xe01e, 0x0)
/usr/src/go/src/pkg/runtime/mheap.c:222 +0x379 fp=0x7f1595b637e0 sp=0x7f1595b637a0
runtime.MHeap_Alloc(0x8a7980, 0xe01e, 0x10100000000)
/usr/src/go/src/pkg/runtime/mheap.c:178 +0x7b fp=0x7f1595b63808 sp=0x7f1595b637e0
largealloc(0x0, 0x7f1595b638b8)
/usr/src/go/src/pkg/runtime/malloc.goc:224 +0xa2 fp=0x7f1595b63850 sp=0x7f1595b63808
runtime.mallocgc(0x1c03c000, 0x6bcfe1, 0x0)
/usr/src/go/src/pkg/runtime/malloc.goc:169 +0xb6 fp=0x7f1595b638b8 sp=0x7f1595b63850
growslice1(0x692900, 0xc2c8780000, 0x59a580, 0x59a580, 0x59a581, 0x7f1595b63978)
/usr/src/go/src/pkg/runtime/slice.goc:125 +0x107 fp=0x7f1595b63908 sp=0x7f1595b638b8
runtime.growslice(0x692900, 0xc2c8780000, 0x59a580, 0x59a580, 0x1, 0x0, 0x0, 0x0)
/usr/src/go/src/pkg/runtime/slice.goc:76 +0xbb fp=0x7f1595b63950 sp=0x7f1595b63908
github.com/tsenart/vegeta/lib.NewTargets(0xc248086000, 0x31a43867, 0x3ffffe00, 0x896080, 0x0, 0x0, 0xc20800f080, 0x0, 0x0, 0x0, ...)
/go/src/github.com/tsenart/vegeta/lib/targets.go:62 +0x5e9 fp=0x7f1595b63b40 sp=0x7f1595b63950
main.attack(0xc208052280, 0x0, 0x0)
/go/src/github.com/tsenart/vegeta/attack.go:101 +0x3c0 fp=0x7f1595b63dd8 sp=0x7f1595b63b40
main.func·001(0xc20800e020, 0x1, 0x1, 0x0, 0x0)
/go/src/github.com/tsenart/vegeta/attack.go:40 +0x73 fp=0x7f1595b63e18 sp=0x7f1595b63dd8
main.main()
/go/src/github.com/tsenart/vegeta/main.go:37 +0x409 fp=0x7f1595b63f50 sp=0x7f1595b63e18
runtime.main()
/usr/src/go/src/pkg/runtime/proc.c:247 +0x11a fp=0x7f1595b63fa8 sp=0x7f1595b63f50
runtime.goexit()
/usr/src/go/src/pkg/runtime/proc.c:1445 fp=0x7f1595b63fb0 sp=0x7f1595b63fa8
created by _rt0_go
/usr/src/go/src/pkg/runtime/asm_amd64.s:97 +0x120

goroutine 19 [finalizer wait]:
runtime.park(0x417d30, 0x8957b8, 0x893a09)
/usr/src/go/src/pkg/runtime/proc.c:1369 +0x89
runtime.parkunlock(0x8957b8, 0x893a09)
/usr/src/go/src/pkg/runtime/proc.c:1385 +0x3b
runfinq()
/usr/src/go/src/pkg/runtime/mgc0.c:2644 +0xcf
runtime.goexit()
/usr/src/go/src/pkg/runtime/proc.c:1445

Support HTTPS

Hi.

Your README gives HTTPS support as a TODO, but after a quick glance at the code, I can't see why it wouldn't already work? I'm happy to contribute, since it's a very useful-looking tool but all my sites use HTTPS only. What sort of changes need to be made to add HTTPS support?

Doubt in rate and workers

One of the doubts I have is the workers flag. For example, I have a rate of 1000 req/s and 1 worker... this mean I'll have one thread sending the 1000 requests?
What about 10 workers? Means that I have 10 threads sending 1000 requests in total right? Not each one.

Is possible to configure Vegeta to have 10 workers sending 1000 req/s each? Not in total.

Error in go 1.3.1

Hi I have following error in golang 1.3.1

../go/src/github.com/tsenart/vegeta/lib/metrics.go:7: import /home/jacekwysocki/go/pkg/linux_amd64/github.com/bmizerany/perks/quantile.a: object is [linux amd64 go1.2.2 X:none] expected [linux amd64 go1.3.1 X:precisestack]

is there any workaround for this ?

Setting high duration's attempts to allocate a ton of memory

I'm using Vegeta that are being considered as alternatives to current production servers, and I noticed that inside a 2gb VM, if you set an overly high duration, in this case 500h (typo'd the m to an h), Vegeta takes some time to think and then usually ends up running out of memory:

goroutine 1 [running]:
[fp=0x7f40498e4b20] runtime.throw(0x9e1885)
    /Users/tomas/Code/gosrc/src/pkg/runtime/panic.c:473 +0x67
[fp=0x7f40498e4b78] runtime.mallocgc(0x10c388d058, 0x100000000, 0x1)
    /Users/tomas/Code/gosrc/src/pkg/runtime/zmalloc_linux_amd64.c:63 +0x344
[fp=0x7f40498e4b98] runtime.mal(0x10c388d058)
    /Users/tomas/Code/gosrc/src/pkg/runtime/zmalloc_linux_amd64.c:614 +0x3f
[fp=0x7f40498e4be8] runtime.makechan_c(0x686de0, 0x218711a00)
    /Users/tomas/Code/gosrc/src/pkg/runtime/chan.c:114 +0xba
[fp=0x7f40498e4c00] runtime.makechan(0x686de0, 0x218711a00, 0xc200122000)
    /Users/tomas/Code/gosrc/src/pkg/runtime/chan.c:141 +0x2f
[fp=0x7f40498e4c40] github.com/tsenart/vegeta/lib.Attack(0xc2000df880, 0x3, 0x4, 0x1388, 0x6651728988000, ...)
    /Users/tomas/Code/go/src/github.com/tsenart/vegeta/lib/attack.go:16 +0x138
[fp=0x7f40498e4f90] main.main()
    /Users/tomas/Code/go/src/github.com/tsenart/vegeta/main.go:80 +0x824
[fp=0x7f40498e4fb8] runtime.main()
    /Users/tomas/Code/gosrc/src/pkg/runtime/proc.c:182 +0x92
[fp=0x7f40498e4fc0] runtime.goexit()
    /Users/tomas/Code/gosrc/src/pkg/runtime/proc.c:1223
runtime: out of memory: cannot allocate 72000012288-byte block (72002109440 in use)
fatal error: out of memory

This isn't a big problem (I would imagine no one really wants to run vegeta for that long), but it would be a good idea to limit or warn users about this shortcoming.

go get github.com/tsenart/vegeta

first I use apt-get install golang and find it installs in the usr/bin/go, then I just set GOPATH variable and then exe "go get github.com/tsenart/vegeta " , then it report error

github.com/tsenart/vegeta/lib

../../go/src/github.com/tsenart/vegeta/lib/attack.go:46: unknown net.Dialer field 'KeepAlive' in struct literal
../../go/src/github.com/tsenart/vegeta/lib/attack.go:53: unknown http.Transport field 'TLSHandshakeTimeout' in struct literal

who can help me to resolve the problem.

Can't set Host header

golang's net/http library seems to ignore a Host header and only uses the value set in request struct or extracts it from url.Host. In order to be able to set a flag like -header="Host: foo.bar" it's necessary to treat that that header different than others.

This works for me:

diff --git a/lib/targets.go b/lib/targets.go
index 9b9739a..b3d70b2 100644
--- a/lib/targets.go
+++ b/lib/targets.go
@@ -63,8 +63,12 @@ func (t Targets) SetHeader(header http.Header) {
        for _, target := range t {
                target.Header = make(http.Header, len(header))
                for k, vs := range header {
-                       target.Header[k] = make([]string, len(vs))
-                       copy(target.Header[k], vs)
+                       if k == "Host" {
+                               target.Host = vs[0]
+                       } else {
+                               target.Header[k] = make([]string, len(vs))
+                               copy(target.Header[k], vs)
+                       }
                }
        }
 }

No idea why the copy of the headers is necessary, it might be necessary for the Host field as well then.

Follow 0 redirects registers each request as error for a redirect

I work in ad tech and we have a server that primarily does redirects to external resources and I do not want their services included in my tests. Since I do not want to follow redirects and most end points give a 302 or a 307, vegeta declares it as an error here. This seems to be good default behavior but it'd be nice if I could supply an option to so that it would not follow and not register as an error.

Do you like any of these options?

  • -ignore-redirects Sets -redirects=0 and ensures status codes in the 300s are not counted as errors.
  • Don't register 300s as errors when -redirects=0
  • Change the default behavior so that 300s don't automatically count as errors.

Feature:Randomize source addresses

Could you please add a feature to allow a CIDR to be specified as the source network to generate traffic. The IP addresses that are part of the CIDR provided would then be added to the interface using the ifconfig command.

An alternate method would to allow the user to specify the list of IP addresses in a file and then have the user also configure their interface with this list of IP addresses (or have the program generate traffic based on all of the IP's configured on a given interface).

I have a use-case where the security devices I test use a src/dst hashing algorithm and will load share the traffic based on these flows. I could do this based on destination address however this would not simulate a real life scenario such as hundreds of users accessing a single web server.

ssl client certs

I wondered if you'd ever thought of supporting ssl client certs?

Histogram reporter

Viewing latencies distributions in a histogram is useful for certain types of data analysis. This has been originally proposed with #78.

SVG not generated

Hi

I'm using the linux64 binary with : ./vegeta -duration=60s -ordering="sequential" -output="out" -rate=20 -reporter="plot:timings" -targets="targets.txt"

However, no SVG is generated, the "out" file is 0 bytes. The text report works fine.

Am I doing something wrong ?

laurent

Perpetual attack

It may be useful to have an attack run for an indefinite duration. CTRL+C must be caught and initiate graceful attack termination. This feature would go well along with the proposed #53.

404s not reported in the HTML5 graph

I have created a targets file with a number of "bad" URLs that return 404s. The 404s are noted in the JSON object 'status_codes":{"200":95,"404":5}', but not in the HTML5 graph, which shows responses as 'OK'. I wondered if this was a defect or purpose design?

Incremental reporters

With the previous work on making most of the data pipeline stream results as they come, it would be great to have a some new reporters which incrementally reflect new incoming data.

report saying network is unreachable + connection refused

Hi,

first of all great tool I am loving it.

I am running a rate 20 attack on a heroku app (mine) on a test plan of around 2K urls for about 1H.

when the reports completes I am seeing lots of:

 dial tcp: read udp 172.25.64.30:53: connection refused
URL dial tcp: dial udp 172.25.64.30:53: network is unreachable
 dial tcp: dial udp 172.25.64.30:53: network is unreachable
Get URL dial tcp: i/o timeout

and here's the report output:

Requests        [total]                         71999
Duration        [total, attack, wait]           1h0m0.201463185s, 59m59.952162509s, 249.300676ms
Latencies       [mean, 50, 95, 99, max]         695.300964ms, 256.873692ms, 1.242270337s, 30.775127016s, 30.775127016s
Bytes In        [total, mean]                   4438273450, 61643.54
Bytes Out       [total, mean]                   0, 0.00
Success         [ratio]                         96.68%
Status Codes    [code:count]                    200:69606  505:717  0:1676
Error Set:

I am running vegeta on a 2.6Ghz i7 macbook pro, OSX 10.9.5 do you reckon those errors are caused by me reaching the OS NIC limits?

Thanks

Body example

Is there an example of what should be placed in the body file, what format should the file be in?

Feature: Different POST payloads for different endpoints

Vegeta does not seem to support different POST request bodies per test. Correct me, if I'm wrong. I have to test multiple endpoints that do no share the same request payload. What if vegeta would support a target file structure like this:

POST http://example.com/create/1 {"test":1}
POST http://example.com/create/2 {"test":2}

and only use the same body if body option is provided?

Linux builds can't be opened

I ran:

wget https://dl.dropboxusercontent.com/u/83217940/vegeta-linux-amd64.tar.gz
tar xvzf vegeta-linux-amd64.tar.gz

And my terminal said:

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

I also tried with the 32-bit version, and it didn't work either.

Option to ignore SSL errors

I have for example cloudflare -> elastic load balancer -> instances and I want to attack a specific endpoint, for example by giving the DNS name of the elastic load balancer. Unfortunately, this doesn't work because it has a different DNS name than the SSL certificate it is using.

go version go1.2.1 linux/amd64 causes the following errors

Hi,

ubuntu 14.04 uses go version go1.2.1 linux/amd64 causes the following errors:

ubuntu@ip:~/workspace$ go get github.com/tsenart/vegeta
# github.com/tsenart/vegeta/lib
src/github.com/tsenart/vegeta/lib/attack.go:45: unknown net.Dialer field 'KeepAlive' in struct literal
src/github.com/tsenart/vegeta/lib/attack.go:54: unknown http.Transport field 'TLSHandshakeTimeout' in struct literal
src/github.com/tsenart/vegeta/lib/attack.go:113: a.dialer.KeepAlive undefined (type *net.Dialer has no field or method KeepAlive)
ubuntu@ip:~/workspace$ go install github.com/tsenart/vegeta
# github.com/tsenart/vegeta/lib
src/github.com/tsenart/vegeta/lib/attack.go:45: unknown net.Dialer field 'KeepAlive' in struct literal
src/github.com/tsenart/vegeta/lib/attack.go:54: unknown http.Transport field 'TLSHandshakeTimeout' in struct literal
src/github.com/tsenart/vegeta/lib/attack.go:113: a.dialer.KeepAlive undefined (type *net.Dialer has no field or method KeepAlive)

what's the recommended go version to install vegeta?

Failed to locate a font file NimbusRomNo9L-Regu.ttf

./vegeta -duration=5s -ordering="random" -rate=50 -reporter="plot:timings"
2013/08/30 17:08:26 Vegeta is attacking 1 targets in random order for 5s...
2013/08/30 17:08:32 Done!
2013/08/30 17:08:32 Writing report to 'stdout'...
2013/08/30 17:08:32 Failed to report: Failed to locate a font file NimbusRomNo9L-Regu.ttf for font name Times-Roman

Added file to osx fonts and to current folder path, but it still doesn't find it.

Plotting a image

Hey,

I'd like to suggest to let vegeta reporter also support plotting into a image. I would need it because I've quite a bunch of result files and would like to compare the results with multiple images.

cheers! 🏮

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.