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
improve test time #150
improve test time #150
Conversation
by configuring the logger itself
Instead of running every test every time, select etcd/consul only some of the time
mainly in adding several routes, which can take a few seconds each, but much faster when concurrent
This is already a huge improvement (~12 minutes overall instead of 60, not counting consul) and shows that something's up in consul, which is way slower than the rest. |
config changes are helpful for tests
df62773
to
2ea8f92
Compare
consul startup/teardown is by far the most expensive, so re-use that one first
as covered in traefik adds traefik_env config for additional passthrough
waiting for sockets may not be enough in slow environments
Consul was by far the slowest, so I decided to make consul persistent, which reduced the test runtime for consul from 26 minutes to 8. Making traefik persistent will be a bit of work because there will be several instances on different ports, so I'd rather do that in a separate PR. I think this is ready to go as an incremental improvement. |
Amazing @minrk ❤️ Thank you! |
add_route
closes #148