chore: aggressive dns caching approach #32
Merged
+74
−34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
context: accidental commit to main here which was immediately reverted
this is a development PR to close #31 which is currently in further testing - i'm going to automate this with scripts and run multiple concurrent runs websites using the selenium loader to be confident going forward
the PR as per this comment (see
Update debug:
) specifically tries to not significantly reduce our ability to trace, but remove any non-critical functionality which can relate to DNS caching, general Google caching or problematic chrome functionality which is highly probable to hangs and therefore 💀 containers.. current changelog: