Server Connection timeout - Replay buffer

[HornetMaX]

So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

Yes MaX, the replay buffer was set to 1024 and the resulting replay size is 977MB. The first part of the session is not contained in the replay.

Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

At any rate, if we ask for a buffer of XXXX MB and GPB cannot allocate that (for whichever reason), then it should probably allocate whatever it can and log a warning somewhere.

The core.exe process allocated about 1GB in taskmanager and there was enough free RAM at the server.

I was talking when 2048 was requested (causing the "connection timeout" reported by PeterV).

[PeterV]

Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

That we can do ofc, we will test that as well.

[dibu]

So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

Yes MaX, the replay buffer was set to 1024 and the resulting replay size is 977MB. The first part of the session is not contained in the replay.

Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

Your test was with a replay size of 2MB but the default replay buffer is 10MB and I'm not sure if you can set less.

I was talking when 2048 was requested (causing the "connection timeout" reported by PeterV).

Peter requested more than 2GB, that's why I've set "replay=2560" (without thinking about the 32bit limit, my fault). With these settings everybody got a "connection timeout". Now next test will be "replay=2000".

[Hawk]

Hawk, are you sure that your replay buffer is 700MB? Both replays files 488MB smells like "replay=500".

This is what is set in my .ini file. 

Code Select Expand

[core]
replay  = 700
texture_quality = 1

Hawk.

[HornetMaX]

So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

Yes MaX, the replay buffer was set to 1024 and the resulting replay size is 977MB. The first part of the session is not contained in the replay.

Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

Your test was with a replay size of 2MB but the default replay buffer is 10MB and I'm not sure if you can set less.

OK, could do the test with 10 or 15 it's fast anyway: 1 lap at aragon (dry) is almost 2MB (single player, offline)

[PeterV]

Peter requested more than 2GB, that's why I've set "replay=2560" (without thinking about the 32bit limit, my fault). With these settings everybody got a "connection timeout". Now next test will be "replay=2000".

I tried getting in with this "replay=2000" same thing "connection time out"

It now has been set too "replay=1900"
I can get in now, we will see what happens with more riders this Sunday.

[PeterV]

It now has been set too "replay=1900"
I can get in now, we will see what happens with more riders this Sunday.

Oke this report was not correct, i'm sorry for that.
I had not set....

Code Select Expand

[replay] save = 1 without this the replay buffersize gets ignored.
Thats why i thought it was oke with a "replay=1900" buffer setting.

Dibu has tested some more (thank you very much Dibu) and he came too the following discovery:
Any value above

Code Select Expand

replay=1592 will give a "connection timeout" aka server crash.
This was tested on Victoria circuit and Silverstone_nds circuit on dry and wet track.

Sundays Testrace will be with more then 1 rider so we can check that as well.

[dibu]

Any value above

Code Select Expand

replay=1592 will give a "connection timeout" aka server crash.
This was tested on Victoria circuit and Silverstone_nds circuit on dry and wet track.

Sundays Testrace will be with more then 1 rider so we can check that as well.

The value 1592 isn't fixed, it's the value for exactly this server. If I run a dedicated server at my working PC (Win10-64) the maximum value is 1278. The maximum value has to be tested individually for each PC running dedicated servers.

A test with a non-dedicated server (local & world) showed a different behaviour. It was not possible to allocate more than 1GB memory for core.exe, doesn't matter how high you specify the replay size. But it doesn't crash even if you choose a replay size of some gigabytes in gpbikes.ini   

It seems that more tests are needed to solve this secret.

[dibu]

@PiBoSo - can you please explain how core.exe calculates the max value after which it starts crashing.
I don't understand it.

I've run some Windows updates at Peter's server today. After the restart the new max value is reduced from 1592 to 1538. Taskmanager and Sysinternals RamMap show some Gigabytes of free memory (standby and completely free).

I also did some more tests with my working pc. As I wrote before here my max value is 1278 despite I have about 10GB free RAM. Even if I start some virtual machines which reduces the free memory dramaticly, the value 1278 still stays the same and doesn't get reduced.

All values are far away from the 32bit limit and there is enough free memory. How does this magic work?

[PeterV]

Okay the race yesterday @ Silverstone wet surface and 5 riders.

Same settings as always, Server replay buffer was now set @ 1500 (the maximum for this server)
The saved replay is 867,2 MB and does not work, wont load due too core.exe.
(tried loading it with a client replay buffer of 10, 100, 300, 600, 750, 1500 mb)

[doubledragoncc]

I had the same if the GPB version I use to ride had the replay buffer set lower to stop cores ie: 450, I would get a core if I tried to watch a 600MB video?

Server and gaming buffers cant be the same as the gaming one will crash if too high when trying to get on certain circuits.

Its the whole damn core issue not being fixed!!!

This is not krp which has all the attention right now!!!

DD

[dibu]

Okay the race yesterday @ Silverstone wet surface and 5 riders.

Same settings as always, Server replay buffer was now set @ 1500 (the maximum for this server)
The saved replay is 867,2 MB and does not work, wont load due too core.exe.
(tried loading it with a client replay buffer of 10, 100, 300, 600, 750, 1500 mb)

Peter, I can run yesterday's replay without problems at my working PC.

The replay size at my local installation doesn't matter. I've tested 1524, 1024 and replay completely remarked in my local gpbikes.ini

My working PC:
I7-2600 @ 3,4 GHz
16 GB RAM (9,6 GB free before starting GP-Bikes)
NVIDIA GeForce GTX970 (Driver 10.18.13.6839)
Windows 10 Enterprise 64-Bit 1511 (Build 10586.494)

Taskmanager shows 1375,9 MB for core.exe when running the replay.

[PeterV]

Well thats weird cause i have roughly the same specs as you mentioned.

My PC:
I7-4770K @ 3.50GHz
16 GB Ram (12,7 GB free before starting GPB)
Geforce GTX 780 3GB Vram TI (driver 10.18.13.6881)
Windows 8.1 64-bit (version 6.3 build 9600)

gpbikes.ini entry:

Code Select Expand


[CORE]
replay = 300 ;;300
bike_shadow = 2048
bike_reflections = 512
texture_quality = 1


GPBikes Graphics settings:

[dibu]

My installation was completely default as I don't play at this PC.
bike_shadow, bike_reflections, texture_quality and replay were not set at my final test.

My graphics settings were 1024x768, Fullscreen=off, Bits=32 bits, Refresh=default, Antialialising=off, Textures size=High, Filtering=Bilinear, Anisotropic=1
Dynamic Shadows, Reflections and Shaders=On, Draw Distance and Model Details=High, 3D Grass=Off

[PeterV]

Replay not set you mean on default off replay = 10 ?

Ill set mine too you're specs and try again tommorrow,
(already tried setting everything too low, still did not work) but i suspect some corrupt memory, because
when i tried too play GPB it cored also, after stopping several tasks in memory , which seemed already closed to me
but where apparently not, like firefox, and 2 others applications i had used before.

So ill try you're settings with a fresh restarted computer in da morning.