Minimum Recommended Server Specs for rFactor 2

Bandwidth:
96 Kbits/sec per user for server populations less than 10
256 Kbits/sec per user for server populations between 10 and 20
768 Kbits/sec per user for server populations between 20 and 30
http://www.lyberty.com/encyc/articles/kb_kilobytes.html

While this is track and vehicle dependent a user can expect something close to these approximations on RAM use:
Approximately 200 MB per server instance for server populations less than 10
Approximately 300 MB per server instance for server populations between 10 and 20
Approximately 400 MB per server instance for server populations between 20 and 30

CPU Usage:
This is also dependent on the server population and number of AI drivers but we would account for at least 250 MHz per server instance and on modern CPU, for example if you have a 2.5 GHz dual core you can run 20 servers (10 per core, 10 * 250 Mhz = 2.5 GHz) on that CPU if you have other requirements mentioned above meet. Floating point unit required.

These are just guide lines, there are many things that can effect performance of the server.

 

Thanks Tim.

 

Will be there dedicated server for linux also or windows is still needed?

 

Excellent!

I should be able to host 10-15 people on my connection.

 

How many AI drivers will we be able to load in a multiplayer race?
And how many human drivers will be able to join a server?

Would be very interesting to know

Really hope there are no more restrictions coming from the software.

 

So if I wan't to host server for 30 players, I need to have internet connection with 24MB upstream bandwidth? Otherwise there will be lag?

 

Thanks for the info Tim!!!!!

+1

 

Graag, can you see difference between bit and byte?
768kbps * 30 = 23000 kbps which is equal to ca 2900 kBps (2,9MBps)

 

my upload is 0,78 Mbps. can I host 8 clients?

 

23000 kbps = 23 Mb upstream bandwith.... houston we have a problem


Salu2

 

What about a native Linux rFactor Server ?

 

I meant 24Mb of course.

 

I don't see a problem with such traffic. We want quality, we must pay for that some price.
Maybe in future it will be optimized a bit. But if you take into account sending data about RealTrack and weather (in both cases for each point of track separately) and more info about telemetry (e.g. better suspension work) there is no way to avoid it.
I also suspect those are aproximated maximal requirements. Maybe there will be possibility to set some kind of throttling or limit precision of sent data.

 

I think you're right.

Maybe I'm reading it wrong, too. Let me check.

 

Yep. You were right. 30 = 2.74 MB, 23Mbit. Or somewhere around there. But those should be considered minimums.

 

Windows initially.

 

Hehe, it's you that managed to confuse me. You put kbps, the list above says Kbps.

 

Well, we have the system specs for run the game. We have the system specs for run the server. And now, we only need one thing more: THE RELEASE!...