Server Lag - It's not the Turrets - Confirmed by dev

[Tiggo]

khorba this is a hard task, mythic didnt manage with over 100 developers KNOWING the code.

They do what they can, but some time we all have to admit warhammer will not be playable on more then 20-30 players in rvr on each side.

[Kragg]

A short reminder that it ain't us.

[K13R]

Sure it is

[Kragg]

Sure it is

We had three parties up and 8 of them were engineer. Don't be a douche.

[Joan]

The lag isn't caused by the Bitterstone Thunderers. I think something in Mandred's Keep causes it.

[Glorian]

It crashed the last time when Order went in in numbers and the moshing startet in earnest.
Glorious Meinhard Bluecher leading the Empire.

First Time it crashed when we fought on the Backside of Mandreds and the melee startet to get in contact.

[Azarael]

It's not them. The problem is memory-related, and I can assure you that nothing about the Engineer class is stressful on memory at all.

What does stress it memory-wise right now is the number of byte[] allocations required for network packets. That's my best guess. It doesn't help that network packet issues scale with the square of the number of players in proximity to each other, because each player must send a state update to all other players within range.

[RyanMakara]

Blaming turrets for server lag...? You've either got to be joking or are looking for the -worst- excuse to disable the use of turrets for the time being, roflmao.

[Glorian]

As of yesterday server Heavy lag and near crash I want to remind that its not the turrets.

And again it seems like mandred is somehow the problem.
Directly before that WE fought through STK with mini mini lag.

[Joan]

I think there is a memory leak caused somehow by something in Mandred's. As Lesti has said above, we fought at STK with no problem.