EVE General Discussion

Well here is an update I found eve searching around

CCP is already considering DynR (Dynamic Remaps is this the offical name for it now?) from the devs so far they commented that shuffeling server loads with curent technology is 'destructive' or in lamen terms forces players to log offs, and they're currenlty working on a way to not cause that so that the load shuffel can happen without the disconnects.

Either way should be interesting I rather be a small lag spike if it means nobody gets booted off then tidi dials a bit down as things speed back up with the load shuffeled off.

-Every SOL is running IN ONE THREAD ON ONE CORE (usually more SOLs on one core, unless its reinforced system).

-You cant partition load on few cores, you cant even divide SOL into grids so if there are 10 battles in one SOL they ALL run in ONE THREAD ON ONE CORE.
-There is no mechanism for live migration, CCP cant just freeze SOL and migrate it to another core :/ It should be easy now that they figured out time dilation - freezing is just slowing time to infinity :)


Sarina Rhoda wrote:
>Correct me if i'm wrong but time dilation wasn't created to fix lag..... Time dilation was introduced to make fights fairer under
>extreme lag conditions. Previously the server would just randomly accept some peoples commands while completely
>ignoring other peoples. This meant some people were able to fight as if there was nothing wrong whilst other people were
>completely locked out.

>Time dilation was simply a method of slowing everything down so that the server has a fair chance and processing
>everyone's commands.


not server, one THREAD bound to ONE cpu core :((( Instead of letting server compute more of the battle they are throttling the battle to "fit" on one CPU.


Zleon Leigh wrote:
>TiDi is implemented because there does not exist a hardware solution that will handle the computation load and also the
>time of flight problem across the net.


Not true, There are FPS games (for example Mount And Blade Warband) currently that run smooth with >200 players bashing each other with melee/thrown/shooting weapons in the face. With server tick time 0.1sec (means steps per second stuff is updated server side). Eve has server tick time 1sec so by extrapolating those FPS games could handle 2000 FPS players at 1sec tick, all unning around, changing directions, waving melee weapons, hitting each other, shooting at each other, all on one map.
EVE doesnt really have directions, when it comes to calculating tracking it doesnt matter where your ship is pointing. EVE is EASY compared to FPS engines, all you need to worry is position and status of incoming/outgoing damage.



+There was an example of optimisation on dev blog ~year ago that showcased some piece of code that was O(n2) for every missile shot (or just object in space, dont rememer). There are still monsters like that in the code.
Stupid client side example - EVERY TIME session changes (jump/undock) your ASSET window is drawn at least 3 times.
-First it is initialized from some dataset in the memory, drawn with default alphabetical order of items.
- then it is REINITIALIZED and sorted according to your selection.
- then it is AGAIN reinitialized and drawn with remembered positions and station item trees open/closed.

Whole GUI was refactored, yet it is still inefficient and is redrawing parts of the screen that dont change at all, it seems nothing is being kept in buffers, compositioning just doesnt exist. You open Market screen and it will call GPU EVERY frame drawing every single font one by one instead of generating that window ONCE into a bitmap buffer and just using it untill something changes. Even Android finally uses proper compositioning and only redraws part of the screen that change - GUI in your phone is smarter than GUI in this game :)




They are working on those things, just toooo slow. There was a time Market was running on same cpu core as the rest of the system, afaik now there are dedicated market nodes. Next step would be enabling separate grids to run on different cores and live migration between CPU cores, preferably over the network so they could migrate them between servers and not only between cpus on same machine.
Of course best case scenario would be rewritting "battle code" into something MULTITHREADED so one big battle can use more than one CPU on a Node (nodes are multi CPU, CPUs have HT) dividing load. Calculating distances, misses, damages, movements, it could all be multithreaded and done at the same time instead of doing it in sequence.



In simple terms tidi SUCKS MONKEY BALLS and is a clear evidence you rather ducttape crap together like minmatar battleship than fix fundamental problems. DROP python server side already.

No, you are correct.

It would be a much better idea to shut down EVE completely for a few years while it is rewritten to function as you describe.

Except, of course, nobody but you appears to want that... and your proposed solutions are problematic at best in light of the information CCP has already provided as to the "hows' and "why's" of the EVE code base.

if I have to update 200 players over each other player's status every 0.1 sec how many operations per second is that?

if I have to update 2000 players over each other player's status every 1 sec how many operations per second is that?

edit: as for the actual topic - experienced TiDi when undocking in a ~50 man fleet from a station.
Cleared within 20-30s after everybody had finished undocking but still annoying.
Of course I might just not have noticed the lag created of undocking such a small fleet before and the TiDi indicator only makes it obvious but still - would never have expected that this creates issues with server load.

Wait til your 800 man blob hits a jump gate.....


Basically, session changes lag the hell out of the system, and tidi makes it screamingly obvious.

Better than black screen. Still ****.

Piloting anything that has to actually move or kite is almost impossible.

I personally would prefer hard limits and proper fights.

I had no problems... Once I realized that it was taking 10x as long to accelerate/turn/etc, just like it was taking them 10x as long to lock/fire/etc.

At least its fair.

You are so FFing dumb, you don't even realize how stupid the nonsense is you are spewing forth

Is it a fleet where individual members are likely to have a lot of bookmarks?

*shrug

I don't have any desire to spend 4-5 hrs doing what normally takes 2.