Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
W
wrk2
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pacer
wrk2
Commits
068808fd
Unverified
Commit
068808fd
authored
7 years ago
by
Gil Tene
Committed by
GitHub
7 years ago
Browse files
Options
Downloads
Plain Diff
Merge pull request #35 from icflournoy/readme_typo_fixes
Fix typos in Readme
parents
34997897
0fc04d3c
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+5
-5
5 additions, 5 deletions
README.md
with
5 additions
and
5 deletions
README.md
+
5
−
5
View file @
068808fd
...
...
@@ -323,20 +323,20 @@ A note about wrk2's latency measurement technique:
The model I chose for avoiding Coordinated Omission in wrk2 combines
the use of constant throughput load generation with latency
measurement that takes the intended constant through
o
ut into account.
measurement that takes the intended constant through
p
ut into account.
Rather than measure response latency from the time that the actual
transmission of a request occurred, wrk2 measures response latency
from the time the transmission
*should*
have occurred according to the
constant throughput configured for the run. When responses take longer
than normal (arriving later than the next request should have been sent),
the true latency of the subsequent requests will be appropriately
reflected in t
e
h recorded latency stats.
reflected in th
e
recorded latency stats.
Note: This technique can be applied to variable through
o
ut loaders.
Note: This technique can be applied to variable through
p
ut loaders.
It requires a "model" or "plan" that can provide the intended
start time if each request. Constant through
o
ut load generators
start time if each request. Constant through
p
ut load generators
Make this trivial to model. More complicated schemes (such as
varying through
o
ut or stochastic arrival models) would likely
varying through
p
ut or stochastic arrival models) would likely
require a detailed model and some memory to provide this
information.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment