Azure / Azure/DotNetty

Suggestion on settings for a large TCP server implementation

Open
#397 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
4.3k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

I've played around with DotNetty for a little bit now, and I have some questions that don't seem to be addressed by any of the documentation I've read, or any issues here.

Is there a resource that anyone can point me to that will help me to understand the configuration I should be running for a large TCP server? This is a TCP server that maintains several thousand (10k+) open TCP connections for a long period of time, sending and receiving data (and processing that data) constantly.

My server is minimally configured, and currently looks like this:

`

bossGroup = new MultithreadEventLoopGroup(1);
workerGroup = new MultithreadEventLoopGroup();

try
{
var bootstrap = new ServerBootstrap();
bootstrap.Group(bossGroup, workerGroup);

bootstrap.Channel();

bootstrap
.Option(ChannelOption.SoBacklog, 100)
.ChildHandler(new ActionChannelInitializer(InitializeChannel));

boundChannel = await bootstrap.BindAsync(port);
}
catch (Exception err)
{
throw err;
}

`

Any help, either suggestions or pointers to other resources, would be appreciated.

Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.