Hi,
How much load does the application have? If the load is low (just a few connections with little throughput), CMP could be disabled to have all client connections sharing the same CPU core. This would make it slightly easier to copy application payloads from the sending connection (it will receive the response payload) to the receiving client connection.
=> The intrinsic load of this service is low. But our F5 applicance is shared on several services.We can not disable the CMP seen our traffic.
Is the protocol some sort of one request followed by one response or is the TCP connection itself multiplexed?
=> I do not quite understand the question but... request followed by one response.
Is it tolerable to add some minor delays to the responses? This would allow you to perform a kind of Nagle for the receiving connection (check every 250ms if the sending connection has buffered response payload which needs to become copied to the receiving connection).
=> 250ms is acceptable.
How could the related pair of sending and receiving connections be identified?
=> The client_1 first attempts to establish the connection that will be used to send messages to the server. then establishes the connection that will be used for receiving messages
Is it an application written for your company or an application using a well known protocol?
=> it's a proprietary protocol from a well-known company
Thanks.