F1Fan07
The server (leased dedicated server at a major data centre): Windows Server 2008 R2 Standard, Core i3-2130 3.40 GHz, 8 GB RAM, 2 x 1TB RAID, 100 Mbps up/down.
Software: rF1 1.255c, mod V8 Factor Unleashed
Configuration: Game launched dedicated server.exe, bandwidth set to 8000 kbps up and down, otherwise default
I have a problem with this server that showed up with a large field (27 cars) and also hosting a rF2 session with about 10 cars. About 4 times during a 60 minute race most of the drivers observed data loss (manifested as cars on track not updating their position properly then suddenly snapping back into place). There is no packet loss or bandwidth problems (I've been testing that for several days), CPU usage during the race is under 10%, network usage is about 4-6 Mbps for 27 cars during a race.
What I've done so far (but not tested with a full field) is to set the Max Data Per Client to 256 kbps (from default 9999) and in Windows have switched Processor Scheduling from Background to Applications. I think that last change may be what I needed to do.
I would welcome input on tuning the system from anyone with experience in hosting on Windows Server 2008 R2
Software: rF1 1.255c, mod V8 Factor Unleashed
Configuration: Game launched dedicated server.exe, bandwidth set to 8000 kbps up and down, otherwise default
I have a problem with this server that showed up with a large field (27 cars) and also hosting a rF2 session with about 10 cars. About 4 times during a 60 minute race most of the drivers observed data loss (manifested as cars on track not updating their position properly then suddenly snapping back into place). There is no packet loss or bandwidth problems (I've been testing that for several days), CPU usage during the race is under 10%, network usage is about 4-6 Mbps for 27 cars during a race.
What I've done so far (but not tested with a full field) is to set the Max Data Per Client to 256 kbps (from default 9999) and in Windows have switched Processor Scheduling from Background to Applications. I think that last change may be what I needed to do.
I would welcome input on tuning the system from anyone with experience in hosting on Windows Server 2008 R2