CODEWITHSUNDEEP
javanetwork-programmingnionetty
erotsppa
erotsppa

Reputation: 15021

Java netty can only take X number of request per second?

Java netty can only take X number of request per second? With the selector approach is it true that it can be a bottleneck in terms of serving request per second? We find that when the traffic is high, clients are unable to connect through, resulting in a time out.

Upvotes: 2

Views: 1916

Answers (2)

user207421
user207421

Reputation: 310913

There's an increasing view that you shouldn't use Selectors, just hundreds of thousands of threads. Selectors move the scheduling process into the application where arguably it doesn't belong. Also they were designed when the alternative was a process per client. A thread per client is orders of magnitude cheaper.

Upvotes: 0

Nikolai Fetissov
Nikolai Fetissov

Reputation: 84169

This is probably not due to selector being a bottleneck, but either due to TCP having too few ephemeral ports on the clients or due to server hitting the file descriptor limit.

Upvotes: 1

Related Questions