perf: add tests

[lffg]

Multi node tests aren't working yet.

Since we're running the performance tests in a docker context (i.e., the controller and each worker live in docker containers), the workers' proxy can't reach the underlying application container (created by Tucano) since they're in effectively different (docker) networks.

tucano/worker/src/proxy.rs

Line 46 in 18423fe

parts.authority = Authority::from_str(&format!("127.0.0.1:{port}")).ok();

This works in a "normal" Tucano setup because in this case the worker is in fact the "host" (in the docker networking point of view). When Tucano creates the underlying application container and publishes (to the host) the chosen port, the worker can access it through 127.0.0.1:{port}.

However, when a worker is running through docker (as we're doing in this performance test setup), it isn't the host anymore, not being able to access the underlying application container through 127.0.0.1 anymore.

[lffg]

Multi node tests aren't working yet.

Since we're running the performance tests in a docker context (i.e., the controller and each worker live in docker containers), the workers' proxy can't reach the underlying application container (created by Tucano) since they're in effectively different (docker) networks.

tucano/worker/src/proxy.rs

Line 46 in 18423fe

parts.authority = Authority::from_str(&format!("127.0.0.1:{port}")).ok();

This works in a "normal" Tucano setup because in this case the worker is in fact the "host" (in the docker networking point of view). When Tucano creates the underlying application container and publishes (to the host) the chosen port, the worker can access it through 127.0.0.1:{port}.

However, when a worker is running through docker (as we're doing in this performance test setup), it isn't the host anymore, not being able to access the underlying application container through 127.0.0.1 anymore.

Fixed per 077918c