These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
 

CCP what's your plan for node crashing

First post
Author
Previous Topic Next Topic
Speedkermit Damo
Republic University
Minmatar Republic
#141 - 2013-12-20 17:24:20 UTC
Leigh Akiga wrote:
Beekeeper Bob wrote:
As a combatant in the current war, I can't say anyone is happy with the current solution. It's simply not acceptable to force your clientele to spend 10 hours online fighting a one hour battle


Hey guy- when you bring Aeons as your logistics and Titans as your drone trigger, you might be contributing to the length of an engagement.

Just sayin'

Love you buddy


Titans actually being used in combat instead of expensive POS ornaments. How terrible.

Protect me from knowing what I don't need to know. Protect me from even knowing that there are things to know that I don't know. Protect me from knowing that I decided not to know about the things that I decided not to know about. Amen.
Xolve
State War Academy
Caldari State
#142 - 2013-12-20 18:45:48 UTC  |  Edited by: Xolve
SFM Hobb3s wrote:
Yep. In b4 'omg i keep getting too far from my dronez' and 'omg bombz'. Even if the fight didn't have any tidi there's no justifyable reason for this many drones. If you check km's from a few months ago there never used to be this many...maybe even 1/5 as much.


Must be from Redditz


GRRRR Dronez.


For posterity:

CCP Veritas wrote:
Red Teufel wrote:
I'm wondering what is CCPs long term plan to fix the node crashingQuestion

Long term plan is the same as the short term plan - diagnose the problem when it happens and fix it. Ideally twice; fixing the root cause and also hardening the system against similar faults.

The causes for the previous three node deaths have been patched on TQ, for example.

It's worth noting that in all recent events it hasn't been the high load that directly causes the node death, but rather errors in the programming that only express at high load or in the kind of highly complex scenarios that large fights contain.
Jessica Danikov
Network Danikov
#143 - 2013-12-20 18:59:17 UTC
CCP Veritas wrote:
Red Teufel wrote:
I'm wondering what is CCPs long term plan to fix the node crashingQuestion

Long term plan is the same as the short term plan - diagnose the problem when it happens and fix it. Ideally twice; fixing the root cause and also hardening the system against similar faults.

The causes for the previous three node deaths have been patched on TQ, for example.

It's worth noting that in all recent events it hasn't been the high load that directly causes the node death, but rather errors in the programming that only express at high load or in the kind of highly complex scenarios that large fights contain.


Lies! Obviously CCP is having node crashes on purpose and intend to keep them in the game. There's a conspiracy to have node crashes! You can't trust the system!

[throws the node on the ground]

...

[throws the whole cluster too]
Lord Zim
Gallente Federation
#144 - 2013-12-20 19:17:45 UTC
CCP Veritas wrote:
It's worth noting that in all recent events it hasn't been the high load that directly causes the node death, but rather errors in the programming that only express at high load or in the kind of highly complex scenarios that large fights contain.

Are the causes for the last 3 node deaths publishable?

Cyno's lit, bridge is up, but one pilot won't be jumping home.

RIP Vile Rat
Pontianak Sythaeryn
The Scope
Gallente Federation
#145 - 2013-12-20 20:02:35 UTC
Nami Kumamato wrote:
But seriously you're talking about 2000 entities fighting 2000 entities resulting in a total of 4000 running scripts (plus adding the neutrals like the system celestial and what not ) and some million or so user command inputs every second. Frankly there are few (commercial) machines at the moment that can handle that and not turn into molten silica.
The only viable solution is for CCP to either multi-thread the code and split the input over different processing channels or to acquire one industrial super-computer that would be used only for cases like Asakai.


Then EVE's server cluster gains sentience, and takes over the world. Do you see what you've done now?
Felicity Love
Doomheim
#146 - 2013-12-20 20:06:23 UTC
Red Teufel wrote:
I'm wondering what is CCPs long term plan to fix the node crashingQuestion


Make the node asplosions more spectacular with better grafix ! ! !!

"EVE is dying." -- The Four Forum Trolls of the Apocalypse.   ( Pick four, any four. They all smell.  )
James Amril-Kesh
Viziam
Amarr Empire
#147 - 2013-12-20 21:40:20 UTC
Vaerah Vahrokha wrote:
James Amril-Kesh wrote:
Mashie Saldana wrote:
The long term plan is to have TiDi go down to 1% instead of 10%. No more node crashing.

Looking forward to waiting almost 7 minutes between drone volleys, almost 17 minutes to turn off a MWD, 1 hour 40 minutes waiting out aggression on a gate, 8 hours and 20 minutes for siege cycle, almost 17 hours between doomsdays, etc.

Forget node crashes, at that point downtime will be the interrupting factor.


Maybe that day you'll understand it's a kind way of CCP to tell you to stop blobbing like mad?

Except that's exactly the opposite of what CCP wants.

Enjoying the rain today? ;)
James Amril-Kesh
Viziam
Amarr Empire
#148 - 2013-12-20 21:43:29 UTC
I tried explaining large battles and node crashes to my roommate (whose current MMO is Path of Exile).

His response? "Maybe they need better servers."

I wanted to smack him.

Enjoying the rain today? ;)
Alavaria Fera
GoonWaffe
#149 - 2013-12-20 21:44:23 UTC
James Amril-Kesh wrote:
Vaerah Vahrokha wrote:
James Amril-Kesh wrote:
Mashie Saldana wrote:
The long term plan is to have TiDi go down to 1% instead of 10%. No more node crashing.

Looking forward to waiting almost 7 minutes between drone volleys, almost 17 minutes to turn off a MWD, 1 hour 40 minutes waiting out aggression on a gate, 8 hours and 20 minutes for siege cycle, almost 17 hours between doomsdays, etc.

Forget node crashes, at that point downtime will be the interrupting factor.


Maybe that day you'll understand it's a kind way of CCP to tell you to stop blobbing like mad?

Except that's exactly the opposite of what CCP wants.

Every single timer goes until downtime.

Let's roll, I'm sure here, too, progodlegend will defeat the blobbers

Triggered by: Wars of Sovless Agression, Bending the Knee, Twisting the Knife, Eating Sov Wheaties, Bombless Bombers, Fizzlesov, Interceptor Fleets, Running Away, GhostTime Vuln, Renters, Bombs, Bubbles ?
Marlona Sky
State War Academy
Caldari State
#150 - 2013-12-20 21:53:07 UTC
Lord Zim wrote:
CCP Veritas wrote:
It's worth noting that in all recent events it hasn't been the high load that directly causes the node death, but rather errors in the programming that only express at high load or in the kind of highly complex scenarios that large fights contain.

Are the causes for the last 3 node deaths publishable?

He just said there was some errors in the programming that they have fixed. Why would they publish the server code anyways??
James Amril-Kesh
Viziam
Amarr Empire
#151 - 2013-12-20 21:55:59 UTC
Who said anything about server code?

Enjoying the rain today? ;)
Lord Zim
Gallente Federation
#152 - 2013-12-20 21:56:50 UTC
Marlona Sky wrote:
Lord Zim wrote:
CCP Veritas wrote:
It's worth noting that in all recent events it hasn't been the high load that directly causes the node death, but rather errors in the programming that only express at high load or in the kind of highly complex scenarios that large fights contain.

Are the causes for the last 3 node deaths publishable?

He just said there was some errors in the programming that they have fixed. Why would they publish the server code anyways??

This is where I point out that you can publish details of what the cause was, without publishing code.

I did not say "publish code", I said "causes".

Cyno's lit, bridge is up, but one pilot won't be jumping home.

RIP Vile Rat
Onictus
Federal Navy Academy
Gallente Federation
#153 - 2013-12-20 22:24:17 UTC
Lord Zim wrote:
Marlona Sky wrote:
Lord Zim wrote:
CCP Veritas wrote:
It's worth noting that in all recent events it hasn't been the high load that directly causes the node death, but rather errors in the programming that only express at high load or in the kind of highly complex scenarios that large fights contain.

Are the causes for the last 3 node deaths publishable?

He just said there was some errors in the programming that they have fixed. Why would they publish the server code anyways??

This is where I point out that you can publish details of what the cause was, without publishing code.

I did not say "publish code", I said "causes".


Yep two out three times they have put up a thread about an unexplained mode failure
Marlona Sky
State War Academy
Caldari State
#154 - 2013-12-20 22:34:30 UTC
Lord Zim wrote:
I did not say "publish code", I said "causes".

Ahhh. Like if there was errors in the code when N3PL use sentries? Blink
James Amril-Kesh
Viziam
Amarr Empire
#155 - 2013-12-20 22:36:34 UTC
Or if there's errors in the code when Boat says in his combined domi/dread fleet (with 1/1/1 gardes/curators/wardens) to log in and out again repeatedly while he's at the airport.

Enjoying the rain today? ;)
Lord Zim
Gallente Federation
#156 - 2013-12-20 22:38:01 UTC
Marlona Sky wrote:
Lord Zim wrote:
I did not say "publish code", I said "causes".

Ahhh. Like if there was errors in the code when N3PL use sentries? Blink

It's as if it's impossible to just be curious.

Cyno's lit, bridge is up, but one pilot won't be jumping home.

RIP Vile Rat
Marlona Sky
State War Academy
Caldari State
#157 - 2013-12-20 23:28:11 UTC
lol I'm just teasing you guys. I would welcome a Veritas dev blog about it all.