From c6f05662899417ad22c4fa3217e6c2ba2d27b5a3 Mon Sep 17 00:00:00 2001 From: Florian Wilkemeyer Date: Sun, 10 Jan 2016 10:56:22 +0100 Subject: Added epoll as event-dispatcher on linux (instead of select()) Note: It will be enabled by default if configure detects that the system has support for epoll To enforce usage of select run configure with --enable-epoll=no --- conf/packet.conf | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'conf/packet.conf') diff --git a/conf/packet.conf b/conf/packet.conf index 3a7ec2c85..1780d1b4c 100644 --- a/conf/packet.conf +++ b/conf/packet.conf @@ -10,6 +10,19 @@ debug: no // How long can a socket stall before closing the connection (in seconds)? stall_time: 60 +// Linux/Epoll: Maxmimum Events per cycle +// Default Value: +// (Maxmimum Supported Connections)/2 +// NOTE: this controls the maximum collected socket-events per-cycle (call to epoll_wait()) +// for example settings this to 32 will allow up to 32 events (incomming data/new connections +// per server-cycle. +// NOTE: Recommended Settings is at least half the maxmimum supported connections +// Settings this to a lower value, may cause lags/delays +// Depending on available CPU Time +// NOTE: This Setting is only available on Linux when build using EPoll as event dispatcher! +// +//epoll_maxevents: 1024 + // Maximum allowed size for clients packets in bytes (default: 65535). // Default Values: // 24576 (Clients < 20131223) -- cgit v1.2.3-60-g2f50