Laurent Demailly
Laurent Demailly
some tests are becoming brittle on circle also, eg https://app.circleci.com/pipelines/github/fortio/fortio/304/workflows/99349c79-0692-4f0e-b935-835e88901143/jobs/3772
circle is getting worse
looks like we also need to make the push to docker from gitlab because despite being in opensource program fortio builds have stopped on https://hub.docker.com/repository/docker/fortio/fortio
started in #494
look at a load test json not grpcping which isn’t really interesting (I am surprised it even does json) There will be a received size histogram, we should add send...
When using the fast client (fortio home grown http client) the request is pre calculated so the size is already known - maybe that feature can be only for that...
I agree that `responseSizes` would be a better name for the current/existing one - that breaks backward compatibility in a small way, not sure if anyone relies on that so...
it shouldn't be too hard to modify the build for that (the build already makes macos and windows builds) - want to give it a try?
one thing to start would be fast client with TLS as right now the fast client is about 2x faster than std go client
@olimpias thanks for noticing, I filled https://github.com/istio/istio/issues/10685 fortio is its own project but istio is using it and that site should be up/it's not expected it isn't