EVE General Discussion

No, you have to wait. TiDi slows down time.


This is what it has to do with lag.

It's not lag. It's a re-definition of the Eve clock tick.

Imagine that when they designed Eve, they had decided the Eve clock should tick 10 times slower than it currently does. Everything would happen 10 times as slowly, but you wouldn't call it lag. It's just that the servers would be working at a very relaxed pace and under-utilized most of the time. With TiDi, they've added the ability to re-define time dynamically.

There is a fix of course it involves putting every single system on its own blade server, however I don't think you will enjoy the $500/month subscription fee.

No it means nothing. The system may be 10% TiDi and the fight is on the other side of the map.

Last time I caught a random TiDi I was in Khanid or something and it was the Goons and Raiden fighting in Tenal. The fact that there is TiDI just means there is a fight happening, the warning is a local count at like 300. If there is a fight next door the system you are sitting in isn't necessarily affected. The systems on a node are not arranged to be connected.

Lag only has a meaning in reference to the software, because the software defines the clock tick which defines when events are judged to be "simultaneous". As long as the processor can do what it needs to do within that timeframe, there is no lag.

If it can't, then the operation queue *lags* behind the clock.

If, however, you fix the clock so that it always stays ahead of the operation queue, you have eliminated lag - the operations can be processed "simultaneously" within the clock resolution of the simulation.

Lag has nothing to do with slowing down. It has everything to do with the processor falling behind the clock so that the idea of simultaneity gets lost and things get out of whack in an unpredictable way.

Yeah, that's not lag, that's just slowing down time, much like changing the speedlimit of a highway to actually increase flow/throughput isn't lag.


The clients are able to send just as many requests as they'd like, the difference is that they're being processed in a more timely manner instead of being queued up, so the server can tell the client "yes, you've told me that already, stop nagging".


Stop harping on about it being a warning system. It isn't a warning system, I do not get a warning before I jump in to a system that the node the system on is heavily loaded, so it's neither a warning system, nor is it particularly early.

You harping on about "well it would be better if the players took it as a warning to commit fewer people so the experience would be better" shows that you're hilariously out of touch with what EVE is all about. What's next, are you going to demand that CCP add in code which kicks in whenever TiDi kicks in, and randomly moves people from both (or all 3, or 4, or 5) sides of a fight until we get down to a sufficient number of people so as to not cause TiDi, because there's a chance that some poor, poor hisec whiner might have to spend a bit more time warping from point to point?

And the bit about "just throw faster hardware at it" comment shows that you have literally no clue how to actually do scalable software.

More or less.

At full speed the server updates the clients once a second. The procs themselves are aren't changing speed, they are running WFO, what IS changing is how fast they are updating the clients. So the Client goes slower, but everything actually happens, opposed to things being bumped out of queued processes and not happening at all or exhibiting random undesirable behaviors.

…because they were on the same node and thus subject to the same TiDi.

@TWHC Assistant

Lets use a traffic analogy with magnets and science.

Pretend a car = packet or a request.

Scenerio one year ago:

Thousands of cars travel down a 5 lane freeway and right before the bridge to get over the river, that freeway would bottleneck into 3 lanes.

A year ago, Tranquility had no speed limits on the freeway leading up to that bottleneck. So, when the cars got to that bottleneck, they'd crash. When they crashed, some NEVER got over the bridge. Those cars that never got over the bridge represent lag and forgotten requests.

Those cars... got lagged.

Today:

CCP decided to implement a speed limit, however not just any speed limit, they installed awesome magnets of science under the road that force all the cars on the road to slow down. The strength of the magnets are based on the traffic on the road many miles (or kilometers) before the bridge. The more traffic, the stronger the magnets get.

Now, all the cars get to the bridge in an orderly, spread out fashion and everyone gets to their destination. Without being left behind. Without lag.

Prior to TiDi, the highsec systems linked to null/low/wherever the fights were causing the lag, just wouldn't have loaded at all, or would be intermittently laggy, which I find much more annoying.