CODEWITHSUNDEEP
performancenetwork-programmingtcptcpclient
JoeGeeky
JoeGeeky

Reputation: 3796

Searching for patterns to create a TCP Connection Pool for high performance messaging

I'm creating a new Client / Server application in C# and expect to have a fairly high rate of connections. That made me think of database connection pools which help mitigate the expense of creating and disposing connections between the client and database.

I would like to create a similar capability for my application and haven't been able to find any good examples of how to apply this pattern. Do I really need to spin up an instance of a TcpClient every time I want to send a message to the server and receive a receipt message? Each connection is expected to transport between 1-5KB with each receiving a 1KB response message.

I realize this question is somewhat vague, but I am starting from scratch so I am open to suggestions. Even if that means my suppositions are all wrong.

Upvotes: 3

Views: 1097

Answers (1)

Vadym Stetsiak
Vadym Stetsiak

Reputation: 1982

Introducing connection pool is a sort of optimization. Premature optimization can be bad.

I would recommend you start develpment without introducing connection pool. When client and server code is stable enough you can create load tests and detect performance problems.

Connection pool is required if time to create a connection is considerable compared to the rate at which data is coming to/from server (load tests should indicate that).

If data from client is send not that often you may not even need connection pool.

Upvotes: 1

Related Questions