zbilun 6a92a2a22e interop-testing: Add concurrency condition to the soak test using existing blocking api ... The goal of this PR is to increase the test coverage of the C2P E2E load test by improving the rpc_soak and channel_soak tests to support concurrency. **rpc_soak:** The client performs many large_unary RPCs in sequence over the same channel. The test can run in either a concurrent or non-concurrent mode, depending on the number of threads specified (soak_num_threads): - Non-Concurrent Mode: When soak_num_threads = 1, all RPCs are performed sequentially on a single thread. - Concurrent Mode: When soak_num_threads > 1, the client uses multiple threads to distribute the workload. Each thread performs a portion of the total soak_iterations, executing its own set of RPCs concurrently. **channel_soak:** Similar to rpc_soak, but this time each RPC is performed on a new channel. The channel is created just before each RPC and is destroyed just after. Note on Concurrent Execution and Channel Creation: In a concurrent execution setting (i.e., when soak_num_threads > 1), each thread performs a portion of the total soak_iterations and creates and destroys its own channel for each RPC iteration. - createNewChannel Function: In channel_soak, the createNewChannel function is used by each thread to create a new channel before every RPC. This function ensures that each RPC has a separate channel, preventing race conditions by isolating channels between threads. It shuts down the previous channel (if any) and creates a new one for each iteration, ensuring accurate latency measurement per RPC. - Thread-specific logs will include the thread_id, helping to track performance across threads, especially when each thread is managing its own channel lifecycle.		2024-11-18 11:57:02 -08:00
..
src	interop-testing: Add concurrency condition to the soak test using existing blocking api	2024-11-18 11:57:02 -08:00
build.gradle	interop-test: add opentelemetry tracing context propagation test (#11538)	2024-09-27 17:22:38 -07:00