EVE General Discussion

its VERY evident that you dont understand! ill put it as plainly as i can...

a metric **** ton of systems are handled by 1 server node and all of eve are separated into these big clusters of systems that are handled by one node or another. and by that i dont mean all of eve is handled by 2 nodes, theyre handled by a fair few nodes.

A server node is a term for server blade, the ones u see in rack cases in big companies, its like your computer at home but more likely, quite a bit more powerful. Almost everything a player does in game in one of these clusters of systems are handled by this one computer. please PLEASE note the use of the word almost in that sentence. Certain things like requiring info from databases (eg market transactions etc...) can request info from other nodes.

but the main point is that theres 1 computer with only a finite amount of processing power able to process what happens in those systems.

before Time DIlation when theres a fleet fight occuring on one of those systems its like back at home on your computer, 600 or more people at a house party wanting to open and use 600 different applications all at the same time expecting it to work and load everything straight away and run smoothly. some will work before others and some people only wanting to write something on notepad will take longer to do so than sum1 opening up a file on photoshop.

You could look at the problem by saying we'll process stuff one at a time and people will just have to wait. this process of waiting for your turn is called SERVER LAG. people hate it cause it means if your fighting in a time sensitive battle, you can die way before ever realising it.

Time Dialation is basically a process that says "woah, calm the **** down, i can process all of your stuff at the same time, just bit by bit. its not ideal i know, and things will take longer to do, but you'll all see stuff happening sooner rather than later."


so just to clarify...

TiDI can only kick in on all systems on the node cause theyre all handled by the same computer resources aka 1 physical CPU + RAM etc...

Eve Onlines Server Architecture cant remap players to different server blades without forcing them to disconnect. and if uve got like 75 systems on that server blade, thats quite a lot of systems to push to other places. and possibly a fair few people that WILL complain that theyre being randomly disconected from eve for no apparent reason. that kinda thing can cause people to loose expensive ships, for example if theyre in a DED complex or an Incursion.

Also theres no stack of CPUs on one server blade. the server architecture is not multi-cpu compatible, and the servers clock speed doesnt go down when TIDi is active.. if anything its running at absolute max clockspeed possible.


... damn i think ive just been trolled :/

On the one hand TiDi is a great feature, however it introduces new problems the people will be bitching about sooner or later.

The time on the TiDi node runs slower, so that it becomes easier to send reinforcements in and continue the fight infinitely. (1min on TiDi node = 10 minutes on other nodes).

It is now easier to react to certain situations. You can see dictors coming closer switch your targets in time so that they can't bubble your supers. You have more time to broadcast for reps as soon as you see that you get yellowboxed.

This happens when you try to fight the symptoms and not the cause.

New Eden became "too small" due to jump drives and bridges. Even if you rf 100 structures all around eden, the defender can wait till the enemy arrives at one of them and deploy his entire blob to this particular system. This would be by far more difficult without the awesome mobility we have now.

Correct. So what the should have been done is limit fleet engagements to what was practical for the given software arch and hardware that meets business goals (can't afford super-shiny boxes) and satisfies the customer base (not just one particular group of players). Instead they continue to reach for the pie....

Dunno.. but no matter what solution they reach for this way it can have the same consequence - ever larger groups will break it, with ever more catastrophic results.

and im pretty sure that the mssql thing is an 8 year old issue too... cause at that time for a start up company it probably seemed a sensible choice given their location, assets and available employee skillpool.

im fairly certain every dev there knows now that unix/linux would probably be greatly preferable, but eves server codebase i guarantee u cant be ported to it without a significant re-write! u might find that Dust514 will be written server side to be used on unix/linux and just coded to allow information to be translated between eve and dust servers, and most likely only possible due to outside investors (eg Sony).

but until ccp have the funds available to dedicate significant dev man years to Eve Online itself, fixes to the current system are the only viable option on the table. and TiDi is a shining example of what can be done on a limited system with some creative thinking and coding.

i for one think Veritas is a f**king legend =)

well it can work on this basis, but it requires ccp to remap a single system to the reinforced node at a downtime before the fight takes place. unfortunately that means people predicting a fight to take place when theres no actual guarantee it will.

even if the fight does take place on the reinforced node as predicted, generally theres several fights that take place in and around the area that can collectively impact the rest of the mapped systems.

so you see it is possible, its just not do-able in a dynamic ad-hoc way currently.

Depends how many large fleet fights happen in the next month. I think the issue will be solved faster with core game play decisions/ functionality. All this hinges on when the crime watch rewrite gets done. Take that off the main core, fix the client lag when you have a large number of pilots in the overview, possibly while breaking it up into more watch list type windows and then we can go back to server side issues.

That sayed the earlier DynR gets in the game the better.

If someone actually filled the fleet fight notification form to gain their own special super node for that massive fleet fight, there would be a lot less baseless crying in this thread.

Also, time dilation across an entire cluster is better than everyone in the cluster having their modules break and client crash.

I too was in Branch this past weekend in ~1400 man fleet fights.

TiDi is the bomb, it rocks, one of the best additions for big blob fests.

I actually got on my first titan kill which was because of TiDi & the fact the titan just couldn't log off like in the old days.

I can only see TiDi getting better & better in the future. Way to go CCP.