Luke Bakken

> have you tried mixing the python and C# versions to see which pairs also demonstrate the problem? No but that's an excellent suggestion. Thank you.

I see the additional latency when combining Python / .NET both ways, but the latency is greater when the publisher is .NET and the consumer is Python. Removing the wait...

Hm, using `crossgen` doesn't seem to affect the initial message latency. Here's what I did: * Enable `PublishReadyToRun` in both csproj files (https://github.com/lukebakken/rabbitmq-dotnet-client-1060/blob/boskjoett-main/consumer/consumer.csproj#L8, for instance) * In the `producer` and...

Next I'm going to test what @bollhals suggests [in this comment](https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/1252#issuecomment-1250013346): > To test this you'd have to send one message, disconnect and build up the connection again in the...

This is the consumer output from [this branch](https://github.com/lukebakken/rabbitmq-dotnet-client-1060/tree/lukebakken/boskjoett-main-warm-up) where the consumer and producer both do a "first iteration" where a connection/channel are created to send one message, then both closed,...

Thanks for the additional testing code @boskjoett. I will update my Python code to do the same to see if the same behavior exists.

As I suspected, the Python code is not affected by the same sort of delays - https://github.com/lukebakken/rabbitmq-dotnet-client-1060/commit/e847411ec834de08fd4083af00630150fb3d75f5 At this time I'll try @boskjoett's latest code with the `main` branch of...

@bollhals this is the edited output from the first two batches of messages sent via the Python producer/consumer programs: ``` CONSUMER received at 2022-09-20 14:12:27.305867, sent at 2022-09-20 14:12:27.305110 -...

Hello @stebet - would you have a moment to give an update [here](https://github.com/rabbitmq/rabbitmq-dotnet-client/pull/1199#issuecomment-1255147777)?

Thanks, I'll review this coming week.