EVE General Discussion

Apparently that is something they are working on conceptually with the DUST devs, I think Veritas said somewhere else that they thought they had it worked out.

It can be abused in the same way that the current degradation scheme can be abused, sure.

Dilation, at least in the first implementation, is a node-level construct. Any solar systems being run by the overloaded node will be dilated. This, while not ideal, is no worse than today - when a node becomes overloaded, all systems running on it suffer.

Yep... I can see plenty of stuff what you would need to track to implement such feature.

My original vision about the "delay" was simple pop up notification (similiar you get before going to lowsec by default) telling that there is time dialation in the area, the que is 3 minutes, the box would remain there while time is counting down and there would be some kind of "leave que"-button to cancel the action if preferred to do so.

Anyways it was good to know that this had been on the table before already. Thanks for the reply :)

There is no mass test this week. Next week's a maybe for TiDi.

What, specifically, are you referring to? I can think of a few things that might fit that description depending on interpretation.



Anywhere from 1 to about 500 systems per node, depending on a great many things. Your garden variety non-reinforced 0.0 node runs around 50-75 systems these days. There are presently 4 nodes per blade, though thinking per-blade is not very useful currently as each node is quite independent and the blades are apportioned to be able to run all 4 nodes at very near full capacity simultaneously.

We call that "non-disruptive live remapping." It's something we absolutely want, but is still a ways away. There is an effort currently to bring disruptive live remapping - the ability to move a system between nodes after disconnecting everyone - up to par. Once that's done, we'll be prioritizing the work of making it non-disruptive against everything else we could be up to.

Time Dilation does help with that effort though - it provides a mechanism which we can use to pause the simulation of a system while it's moved, so we have some progress on that front without even trying

Are "nodes" VMs running on the blades? Is there a software limitation which prevents you from moving VMs off a blade and giving that one node more of the blade's power, allowing it to handle a single overloaded node better?

Could one 'disruptively' move systems off an overloaded node that are currently devoid of players, so the interruption isn't noticed by anyone in-game? Without players in them, would moving about empty systems even help?

Thanks for your answers. :) I'm sure EVE provides some... unique software requirements and limitations to keep it running smoothly, but I know with VMs we can move them between blades with effectively no interruption in service.

Keep up the good work. :D

Yes keep up the good work CCP. Some of us truly appreciate it.

I think there is more to it than that.

If a node running multiple solar systems gets overloaded by a big fight in one system it will go into TiDi, taking all the solar systems running on that node with it. TiDi is not limited to reinforced nodes. If at that point CCP could do dynamic load balancing they could move the big fight over to a reinforced node right in the middle of the fight.

All the people in the other solar systems are now happy because they are not in TiDi while they are just doing normal stuff.

All the people in the big fight are happier because the got a reinforced node all to themselves.

Now, if a fleet fight form was submitted and the solar system was already on a reinforced node, dynamic load balancing would not help. So it only helps for unplanned fights.