19-10-2015, 06:05 PM
On the server issues:
I think those issues are usually two-fold, one is the bandwidth and the other is the memory requirements. Each participant is grabbing a piece of memory, so would be usefull to watch the RAM usage during heavy workloads. If the systems starts to swap out to the harddrive, it needs more physical RAM.
Hickups at the start are probably mainly caused by bandwidth problems, AFAIK rfactor only transmits hi-rate updates of cars around you, cars on the other side of the circuit are not updated as often. At the start everything is packed together so everyone needs hi-rate updates from everyone -> boom.
Also, some client machines are probably quite taxed trying to render 24 cars in super-glossy resolution at the start and have trouble sending out position data to the server in time, so the client and the server get out of sync when reasoning about the state of the world. This would be seen as warping.
I dont know how to solve all of this, the only thing coming to mind is beefing up the server on race day, maybe using a cloud service where you simply pay by the hour. It is possible to spin up a super-beefy 16-core monster on amazon and shut it down after 3 hours. That would probably cost onyl a few $.
Other than that, the first race was great, finishing 6th was more than I could ask for. The second race left me vertically parked against the hayballs under the bridge at which point I called it a day.
I think those issues are usually two-fold, one is the bandwidth and the other is the memory requirements. Each participant is grabbing a piece of memory, so would be usefull to watch the RAM usage during heavy workloads. If the systems starts to swap out to the harddrive, it needs more physical RAM.
Hickups at the start are probably mainly caused by bandwidth problems, AFAIK rfactor only transmits hi-rate updates of cars around you, cars on the other side of the circuit are not updated as often. At the start everything is packed together so everyone needs hi-rate updates from everyone -> boom.
Also, some client machines are probably quite taxed trying to render 24 cars in super-glossy resolution at the start and have trouble sending out position data to the server in time, so the client and the server get out of sync when reasoning about the state of the world. This would be seen as warping.
I dont know how to solve all of this, the only thing coming to mind is beefing up the server on race day, maybe using a cloud service where you simply pay by the hour. It is possible to spin up a super-beefy 16-core monster on amazon and shut it down after 3 hours. That would probably cost onyl a few $.
Other than that, the first race was great, finishing 6th was more than I could ask for. The second race left me vertically parked against the hayballs under the bridge at which point I called it a day.