EVE General Discussion

one thing TiDi does amplify the suckyness of..

ECM !

Because of tidi

That's not an example of TiDi working against either side. Since bother are under the affects of TiDi, there is no advantage, and the more prepared, aggressive side wins the engagement.

The reason that TiDi favors the party that is reacting is that they are more likely to have players incoming from systems that are not affected by TiDi. Those incoming players are acting 10 times faster than the players at the point of engagement.

It really becomes apparent when you extend the process. Let's say TiDi = 1% or even 0.00001%. With time almost at a stand-still for the attackers, the group with more players and resources to leverage overall has all the time they need to bring in enough logistics, firepower, ewar, etc. to completely turn the tide of the engagement. It is only "fair" when, as you point out in your example, all participants, direct, indirect, current, and future, are affected by TiDi in the same way.

Maybe people should just expect systems to enter TiDi and plan accordingly, there is no prize for second place and forum whining is not going to change anything.

I was thinking about this last night (actually, I had a dream about it). TiDi actually gives the smaller side a chance to bring balanced numbers to the fight as well. While the system that the titan is in might be dilated to hell and back again, the rest of the region isn't, giving the smaller side a chance to call for backup from surrounding systems where (if the corp/alliance is at all decently organized) they can assemble one system over and then jump/bridge in to support the titan.

The issue with TiDi I think is the point at which it "kicks in". Let me say that I am not a computer engineer so I don't know how feasible this is, but if they could set it up so that the load time to enter a system (either by jumping into the system or bridging in) was not effected by dilation (which is basically artificially induced lag so that everyone is operating at the same level, or at least that is the intent though it doesn't seem to actually work all that well IMO) that would help balance the numbers issue, though not necessarily the effectiveness of one side relative the other.

What I think should be done, personally, (and again, I don't know how feasible this is), is for TiDi to be a region-wide "resource redistribution". Basically if system x of region y has 4000 people in it, all the other systems in the region dilate (in an inverse relationship to how many people are in the system, so a system with 0-5 players in it will dilate to a greater extent than a neighboring system with 100 people in it) in order for the server to allocate additional computing power to system x. System x might still dilate, but instead of dilating to 10%, maybe it would only dilate to say 50%, where the game is at least still reasonably playable and enjoyable. This also has various "meta-benefits", in that it allows one side to still reap the benefits of "surprise" (instead, under the current TiDi system, those advantages are lost because while only 1 minute might pass by in a dilated system, 30 minutes would go by in the neighboring systems giving the side that was taken by surprise ample time to bring in a fleet of reinforcements and neuter the effects of being caught with your pants down) because not only will the dilation not be quite as severe (hopefully) but the entire region will be, in effect, "locked down" making travel and thus reinforcement difficult, if not impossible. This shouldn't be an issue to two fleets in a pitched battle where both sides know whats coming, since the systems in which the two sides form up in shouldn't be hit by the dilation quite as hard and making the 1-2 jumps to the battlezone wouldn't be as severe as traveling from the other end of a region or even a neighboring region. This also means that the side thats better prepared and organized for the fight (taking the effects of the dilation into account) is at a better advantage which introduces a new element of skill or whatever that will need to be taken into account during war time, rather than which side can out-dps or out-tank the opposition. Basically, it creates a more tangible "high ground" in space, the side that outmaneuvers the other and engages on its own terms at the location of its choosing will be at a greater advantage if it can leverage the distance the other side would have to travel to reinforce its fleet against itself.

And if you think about it, generally half the galaxy is sitting more or less empty, I don't know what the server infrastructure is like, but if half the systems in say... Geminate are empty (or something close to it), is it really worth allocating a full load of processing power to making sure that system is functioning smoothly? If you distributed TiDi galaxy wide, the entire galaxy might dilate to 90% (which most people probably wouldn't notice) but perhaps System X would be running at 90% instead of 10%. I heard they allocated the Jita super-node or whatever to the fight the other day to try to speed things up (which really just slowed down Jita) so I suppose this is theoretically possible, though I think given the amount of people in Jita at any given time they should probably never do that one again lol. Maybe the answer is having a spare super-node or two just for when these sorts of fights pop up that aren't really used otherwise?

My .02 ISK anyway.

meh, nobody really liked BOB anyway...

Surely TiDi only exists till CCP work out how to reinforce nodes willy nilly :D

In X years i hope TiDi is a thing of the past when we all have door to door fiber, servers more powerful than the intire current cluster etc and so forth :)

You can only run one system on a CPU because the order that the computations is done matters and the overhead from talking to other CPUs, waiting around for the results, and putting those results in the right order would negate any gains.

It has nothing to do with Python and everything to do with running a complex real-time simulation.

For this type of application, where order and timing are critical, multicore processors only have an advantage when running multiple applications (i.e. a 2 core processor can run 2 systems almost as well as a 1 core can run 1). It's primarily the overhead in keeping putting the results in the right order that negates the advantage.

Different computational problems benefit from different architectures differently. General home computing benefits massively from multiple cores. Generally speaking, Simulations like an EVE node don't.

Welcome to the real world.

They almost won for having executed almost flawlessly.