Post: #25

(11-29-2019 04:42 PM)Coruja Wrote:  UseAsyncNetwork, NetworkThreads and NetworkThreadPriority got removed from sphere.ini about 4 years ago. I don't know if these settings are related to this problem, but try set them to default value or remove from sphere.ini

Anyway, maybe your sphere.ini is outdated and this is making your server use outdated settings and also lack some new features, so try update the whole sphere.ini to check if this can fix something

Code:

// Use asynchronous data sends (changing this setting at runtime may produce unexpected behaviour)
//  0 = Off
//  1 = On
//  2 = On for 4.0.0+ game clients only
UseAsyncNetwork=0

// Number of network threads. Clients are distributed evenly amongst each thread. Set to 0 to not
// use a separate networking thread.
NetworkThreads=0

// If network threads are used, this controls the priority they are assigned.
//  0   = Idle
//  1   = Low
//  2   = Normal
//  3   = High
//  4   = Highest
//  5   = Real-time
//  255 = Automatic (recommended)
NetworkThreadPriority=255

Thanks Coruja, I actually used the default sphere.ini from build (11/26), when I noticed the CPU usage for NetworkThreads and spheresvr, I changed the settings using another combination.

I tried now using the latest version of sphere.ini, the problem persists.

What is the recommended server configuration for using sphere 56d?