EVE General Discussion

Let's go back to the time when you had a big battle with 600 guys in local and the following would happen:

- Modules not even activating
- You being desynced for an hour without you knowing
- Warping on grid and waking up in a clone bay. An hour later...

And all the other crap that happened which are too numerous to write down. Ever heard the story about the battle in which 1 side jumped through a gate, and a 100-man fleet just woke up in clone bays because the other side had so many people on grid, that the jumping party couldn't even load grid?

TiDi was implemented for a reason, while I must admit I don't know the exact reason but I think it had something to do with giving the server more time to do what it has to do so all the bad stuff didn't happen.

It just seems like the threat of tidi puts people off doing anything large scale, especially if its short notice.

"Hilariously large fleets created to deter actual fighting cause crippling lag" and "tinfoil is just easier to use than realising you have spies amongst your ranks"

Alternatively they could just do what any normal person would do and multithread their server code. I know it's legacy code and will be a large investment, but it's already a joke that their solar system servers have to run on a single core (because back in the day, CPU power grew primarily on clock speed whereas now it grows on additional cores), and it's only going to get funnier as time goes on.

Tidi was a stopgap measure. It allowed them to give the server more time to get through the event queue so that they could still run everything on a single heavily overclocked core. At some point the promoted to "the fix" and now it's a burden. Things like BIAB help, but in the long run the solution has to be modernising their server code.

Yeah, this. First hand experience here, been blown up ship AND pod by smartbombs while about to come out of warp on a gate. It's kinda fun .

EDIT: as a side note, also seen it done to others while in a smartbombing gatecamp but not smartbombing myself.

BUWHAHAHAHAHAHA!
"Just multithread it"
Yeah. No. Id rather light myself on fire and let a thousand rabid chihuahuas feast upon my still living charred corpse.


TiDi is an efficient and much loved replacement to the old method.. The black screen of death.
Once upon a time there was no controlled slowdown. You either got in and lagged like a dead monkey trying to play tennis or you got treated to the black screen of "go make dinner while your client crashes and you die".

I know I know.. saying TiDi is good even though it harvests your soul to sit in -10% TiDi seems weird... but trust me the alternative is far worse.

• TiDi is a goddamn luxury compared to what came before it
• Smartbombs have always damaged ships in warp, it's just less noticeable at 100% speed
• The new TQ hardware coming in a couple of months time (plus the recent and ongoing software improvements like BitB) are all helping to make TiDi occur less often.

In summary, your post is bad and you should feel bad.

TIDi cancer? spoiled kid. before Tidi when we jumped into a large fight what hapepned is that you would wait between 30 minutes to 2 hours with a black screen. then 30% of people woudl disconnect, other 33% would load grid and be unable to use any controls of the ship. Other 13% would be able to laod and press fire a ingle time per hour. The rest would wait another hour and try their luck again...

Introducing paralelism on a task whose bottleneck is I/O with the database and sincronization is not always the best thing to do. If you cannot change the model to remove data dependency you are not going to solve anything. Usually it is better to remodel the system. The thigns that are needed for an eve fleet battle are NOT huge and do nto justify even a single modern CPU being bottlenecked.

Physics simulation of particles is a classic example of problem that in theory is a prime candidate for paralelization, but when you do it you incur in the need of a more complex iteration model and syncronization mechanisms that downgrade the performance massively> The result is that you need then to use several CPU to match what you could earlier do with a single CPU. Of course, if you can just throw even more CPUS at the problem you have a gain, but the cost involved is high, therefore it is not always a good solution.

But we already know that's not the bottleneck. The bottleneck is CPU. This is why when you fill in that form they use a reinforced server, which is one where most of the cores are shut off on the CPU and used as a heat spreader while the core in use is overclocked like crazy. A single modern CPU has multiple cores, all (or most) of which will be used by most CPU heavy game servers. EVE doesn't. A single core has to process all of the information coming in from the thousands of players in the system. Even on a modern CPU, that is too much.