[fixed] headless server: 100% cpu load on map load

[treba]

my dedicated server is at 100% cpu load during map load until all clients have finished loading.
as i have a really slow computer, it takes much longer if i'm in the game, compared to a game with fast clients. but in both cases, the server is under heavy load during the loading process.

after the game starts, it's all fine.

actually, that's all not much of a problem, but if we want to run multiple servers on one system, it would make running games choppy.

the server is a vps with a 3ghz qemu cpu

[tomreyn]

Which version or revision is this report about exactly? Thanks.

[softcoder]

Try svn rev 2801 to see if this is resolved

[treba]

actually it's better now, but not really resolved as it's still at around 80% cpu load. maybe somebody else can reproduce this with another maschine?

[softcoder]

This occurs only during load (while waiting for players) right?

[treba]

yep

[softcoder]

svn rev# 2812 introduces the following:

Server host:

Code: [Select]

NetworkServerLoopGameLoadingCap=100
NetworkServerLoopGameLoadingCapSleepMillis=1
Clients:

Code: [Select]

NetworkClientLoopGameLoadingCap=100
NetworkClientLoopGameLoadingCapSleepMillis=1
These are hard coded defaults and are not in glestuser.ini by default. You may override them by adding the entries and tweaking the values.

The first cap entry is # of loops waiting for the game to start before we let the CPU rest (sleep). The second is the # of milliseconds to sleep.

Previously the values were hard coded at 300 and 1 (now they are 100 and 1 and overridable)

[treba]

just tested it. with standard values, it took a little bit less but still much.

than i tested it with 10/10 and it was much better. is there any disadvantage with that values?

[softcoder]

just response time for game ready, and in the case of 10/10 its check every 10 loops for game ready and sleeping 10 milliseconds, which doesn't seem harmful to me. I'll change the defaults to 10/10 at least for the host.