-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support benchmarking of multiple HTTP(S) endpoints #76
base: master
Are you sure you want to change the base?
Support benchmarking of multiple HTTP(S) endpoints #76
Commits on May 8, 2019
-
handle EPOLLRDHUP and EPOLLHUP as read-events, so dead connection can…
… be closed and re-opened
Configuration menu - View commit details
-
Copy full SHA for 9bea8ae - Browse repository at this point
Copy the full SHA 9bea8aeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2e001cf - Browse repository at this point
Copy the full SHA 2e001cfView commit details -
Configuration menu - View commit details
-
Copy full SHA for c8395f0 - Browse repository at this point
Copy the full SHA c8395f0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0dded10 - Browse repository at this point
Copy the full SHA 0dded10View commit details
Commits on May 14, 2019
-
src: handle EOF as reconnect without error
When EOF gets received, it should reconnect the socket without increasing error counter. Otherwise we could see socket read errors even in case of ordinary reconnects.
Dongsu Park committedMay 14, 2019 Configuration menu - View commit details
-
Copy full SHA for 5851d46 - Browse repository at this point
Copy the full SHA 5851d46View commit details
Commits on May 15, 2019
-
LUA API: force reconnect when wrk.thread.addr is set
This change forces a reconnect of all connections of a thread when wrk.thread.addr is set from a LUA script. wrk.thread.addr has always been writeable from LUA, but the actual socket connection was never updated in wrk'c C code. This change enables LUA scripts to connect to multiple servers, extending the feature set of wrk. Signed-off-by: Thilo Fromm <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 9ff7b65 - Browse repository at this point
Copy the full SHA 9ff7b65View commit details -
Merge pull request #1 from kinvolk/dongsu/fix-reconnect
Re-connect when peer closes the connection
Configuration menu - View commit details
-
Copy full SHA for e055282 - Browse repository at this point
Copy the full SHA e055282View commit details -
Signed-off-by: Thilo Fromm <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for ecc99a2 - Browse repository at this point
Copy the full SHA ecc99a2View commit details -
reconnect: call reconnect from the correct LUA API function
Signed-off-by: Thilo Fromm <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 0052ff8 - Browse repository at this point
Copy the full SHA 0052ff8View commit details -
reconnect: fixed potential segfault
Signed-off-by: Thilo Fromm <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 7eded81 - Browse repository at this point
Copy the full SHA 7eded81View commit details
Commits on May 16, 2019
-
Merge pull request #2 from kinvolk/t-lo/thread-force-reconnect-when-a…
…ddr-is-set LUA API: force reconnect when wrk.thread.addr is set
Configuration menu - View commit details
-
Copy full SHA for bebf908 - Browse repository at this point
Copy the full SHA bebf908View commit details
Commits on May 18, 2019
-
Signed-off-by: Thilo Fromm <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 996f8c4 - Browse repository at this point
Copy the full SHA 996f8c4View commit details
Commits on Aug 11, 2019
-
Generic multi-endpoint support for upstreaming
This change makes multi-endpoint support more generic, with the motivation of making this feature useful for upstream. The LUA script 'multiple-endpoints.lua' allows for specifying an arbitrary number of HTTP(S) endpoints to include in the benchmark. Endpoints will be connected to in a random, evenly distributed fashion. After a run finished, the overall latency will be reported (i.e. there's currently no break-down per endpoint). The main purpose of running a benchmark over multiple endpoints is to allow benchmarking of e.g. a whole web application instead of the pages and/or restful resources that make up said application individually. Signed-off-by: Thilo Fromm <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for b85ddb7 - Browse repository at this point
Copy the full SHA b85ddb7View commit details
Commits on Jun 8, 2020
-
Merge remote-tracking branch 'upstream/master' into t-lo/upstream-mul…
…ti-endpoint-support
Configuration menu - View commit details
-
Copy full SHA for 82c1642 - Browse repository at this point
Copy the full SHA 82c1642View commit details