- 19 Sep, 2022 1 commit
-
-
Poul-Henning Kamp authored
-
- 17 Sep, 2022 1 commit
-
-
Nils Goroll authored
-
- 15 Sep, 2022 8 commits
-
-
Martin Blix Grydeland authored
Releasing 7.2.0
-
Martin Blix Grydeland authored
-
Nils Goroll authored
Ref d72caa00
-
Nils Goroll authored
I think that the other late additions to changes.rst do not qualify for the release docs. Thank you to Dridi and phk for preparing most of the docs and thank you to Martin for the opportunity for some last minute additions.
-
Nils Goroll authored
The #3830 info is taken from 137d9814
-
Nils Goroll authored
due to vrt_ctx change in a8483cf5
-
Nils Goroll authored
Ref c23ef4c3 870f16ce Closes #3846
-
Martin Blix Grydeland authored
-
- 12 Sep, 2022 3 commits
-
-
Nils Goroll authored
-
Dridi Boukelmoune authored
-
Lachlan Abbott authored
When a request comes back from the waiting list, it is accounted for in the client_req counter, despite not being a new request. To avoid the spurious increments, a request is counted only after leaving the state machine for good. This has no effect on when the client_req increment becomes visible since it is part of the "wrk" group in the first place. In 2e66e0b9 the client_req increment was moved from the request state machine (R_STP_TRANSPORT) to individual transport. This patch can't be reverted because shortly aftwerwards the ESI transport changed in 2c59afe2 and now runs the R_STP_TRANSPORT step and the client_req counter does not count sub-requests. Refs 2e66e0b9 Refs 2c59afe2
-
- 07 Sep, 2022 3 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
- 06 Sep, 2022 1 commit
-
-
Poul-Henning Kamp authored
Varnish is not subject to CVE 2022 37434, we never use "extra" data.
-
- 05 Sep, 2022 6 commits
-
-
Dridi Boukelmoune authored
Otherwise a source tree bootstrapped --without-config would not distribute the contrib script and test, that are needed for the distcheck target and general redistribution.
-
Dridi Boukelmoune authored
There seems to be no output right now, and the test case is failing.
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
-
Geoff Simmons authored
Restructured so that: * 'Upgrading' is limited to work that has to be done to upgrade from a current deployment to the new version. * 'Changes' is a comprehensive, user-level description of changes and new features.
-
- 01 Sep, 2022 1 commit
-
-
Nils Goroll authored
-
- 31 Aug, 2022 1 commit
-
-
Nils Goroll authored
-
- 30 Aug, 2022 7 commits
-
-
Dridi Boukelmoune authored
I was initially going to align the output only if the nonstandard column(1) command was present.
-
Dridi Boukelmoune authored
As I was comparing the output of two varnishstat executions that were captured after a fresh start of varnishd followed by the workloads to compare, I realized diff(1) was giving me a hard time, and git-diff(1) barely improved the situation. Looking for generic command line utilities to compare metrics I wasn't able to find anything. So instead I came up with the output format I thought would help me spot interesting differences and came up with a format inspired by the unified diff, with a twist. I wanted metrics to be vertically aligned to easily see differences in orders of magnitude and reduce the noise to a minimum. The result is that taking this detour to script varnishstatdiff sped my research up ultimately. This should hopefully be portable to POSIX systems.
-
Dridi Boukelmoune authored
This will add scripts we ship to the PATH, so they remain reachable for VPATH builds.
-
Dridi Boukelmoune authored
This removes the ability to run in -i mode without finding a makefile to derive ${topbuild} from, which shouldn't exist in the first place.
-
Dridi Boukelmoune authored
In the top makefile we make the check target depend on the all target, so we ensure that everything is built before we start using varnishtest.
-
Dridi Boukelmoune authored
-
Nils Goroll authored
I accidentally broke the installation in 9f996c1f
-
- 29 Aug, 2022 8 commits
-
-
Nils Goroll authored
Stumpled over (unsigned:1)var = FEATURE(...) not being true when it should have been... Related: We might want to remove some redundancy from common_param.h...
-
Nils Goroll authored
Motivated by and in preparation of #3826
-
Nils Goroll authored
The filter check does not make sense in the context of bereq and the macros became overloaded with two different cases. Motivated by and in preparation of #3826
-
Nils Goroll authored
-
Dridi Boukelmoune authored
The goal is to prevent grace mode from adding load to a saturated Varnish server. A background fetch entering the queue will block the client task that triggerred it until it starts its execution, and reaches the point where it no longer needs to hold onto its req. On a saturated system this can result in significant client latency despite a grace hit. A stale object can be served until the end of its grace period, at which point a regular fetch would be attempted, and eligible to queuing if that is still necessary. This turns the Pool_Task() failure dead branch from VBF_Fetch() into a reachable one.
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
A fetch transaction is always successfully scheduled or queued, so the fetch_no_thread counter can only ever stay at zero. The plan is to relax this for bgfetch tasks.
-
Dridi Boukelmoune authored
The new macro is added to better reflect operations that cater to the thread reserve. It also enables the allocation the right number of reserve heads in struct pool, instead of having one for each priority. It grants the possibility of priority classes so low that they wouldn't be eligible to queuing, without wasting space with needless queue heads.
-