If TiDi is node wide - then the implementation is completely wrong.

I've changed my mind about TiDi breaking low populated systems. If TiDi kicks in I know a blob fleet is on its way. Thanks for expanding local!!!

If the node is getting hammered so much that it has to slow the game down to 10% of its normal speed then why should it work any faster on other systems the node is running? It somehow magically gets more cpu time out of thin air to run the other systems on the node?

How could it not be node wide? It's the node that is having trouble handling the requestsGǪ
GǪexcept that node assignment and geography aren't necessarily linked.

Gee, I was able to lock people and the system was down to 10%. Stop whining. Everyone but you thinks time dilation is an excellent solution to reducing the EFFECTS of lag (since there's no way to remove lag completely, stop telling them to "fix the game" when players keep finding new and creative ways to break it)

it's just a matter of where you draw the magical time difference. As far as EVE the universe is concerned some part of it needs to run slower so the entire galaxy doesn't collapse. That can be at the fleet planetary system level, node level (cluster of PS's), or the entire universe (superset). The line should have be drawn at PS's level. CCP implemented it at node level because they can't handle the incoming fleets into the target battle system instead of dynamically adding PS's to the dilation zone as needed (they went with simpler coding). That's what's screwing non-fleet participants over.

Doesn't excuse other problems it is causing...

Now Zleon, with that knowledge and given parameters to work with - how is CCP supposed to just TiDi a single thread on a node which is overloaded?

PS: no, as I said earlier.. they can't pull threads from the node to mildly reinforce it yet, as the pleyers would be disconnected.

GǪsuch as?

Node size + blue/red check + no neutrals allowed in.

The point is is, you can have open-end resource-consuming batltles that may work as best as possible, but not necessarily well, or limited battles assured to work well within their allotted resources.

'Cause the problem is the one thread (or probably at most 3 threads) causing the overload, not the entire node. So dilate the one thread and there you go... there is no reason to hit an entire node with TiDi.

This issue is closely related to design simulations done in the engineering community - time scaling and microtime problems have been worked on for years in EDA. Maybe CCP needs to consult with them.

Like maybe the outbreak of server crashes since the TiDi release? Spreading outbreaks of system lagg reported from all over?

I would suggest if you don't know what you are talking about, don't talk.

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.

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.

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

*snip*

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.

please fix lag and combat altogether.

Introduce new Area of Effect weapons, which instantly finishes blobs. If someone blobs and stands still, weapons of mass destruction can hit the centre of the blob and wipe them out.

Pilots will have to think smaller, maneuverable groups.

please fix lag and combat altogether.

Introduce new Area of Effect weapons, which instantly finishes blobs. If someone blobs and stands still, weapons of mass destruction can hit the centre of the blob and wipe them out.

Pilots will have to think smaller, maneuverable groups.

Also, they should be able to be fired through cynos.

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

Gee, I was able to lock people and the system was down to 10%. Stop whining. Everyone but you thinks time dilation is an excellent solution to reducing the EFFECTS of lag (since there's no way to remove lag completely, stop telling them to "fix the game" when players keep finding new and creative ways to break it)