You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently load-testing nginx with drill. It's always the same file, which is requested and always the same content delivered.
It came to my mind, that the logged $body_bytes_sent in the nginx access log vary from request to request. This should not be the case, since it's the same file.
I'm running the current master and build it with:
cargo run --release -- --benchmark example/benchmark.yml
As you can see, the body is only fully downloaded, if the body gets assigned. Obviously for some reasons, drill does behave different with the assign action.
I haven't been able to produce a working patch for drill yet, but the assign was my workaround.
What has to get patched, so that drill downloads the full file by default?
The text was updated successfully, but these errors were encountered:
I'm currently load-testing nginx with drill. It's always the same file, which is requested and always the same content delivered.
It came to my mind, that the logged
$body_bytes_sent
in the nginx access log vary from request to request. This should not be the case, since it's the same file.I'm running the current master and build it with:
cargo run --release -- --benchmark example/benchmark.yml
The file behind
/1m.bin
is 1 Megabyte of random data.As you can see, the body is only fully downloaded, if the body gets assigned. Obviously for some reasons, drill does behave different with the assign action.
I haven't been able to produce a working patch for drill yet, but the assign was my workaround.
What has to get patched, so that drill downloads the full file by default?
The text was updated successfully, but these errors were encountered: