Wow Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Tuesday, 26 March 2013

Handling server overload

Posted on 23:00 by Unknown
TiDi is a bad answer for a problem in EVE: as players are usually distributed among the various star system groups (servers), providing low load. These servers are unable to support if thousands of players happen to jump on one system. Such events are rare but crucial moments, shaping EVE. TiDi tries to handle this with slowing down time locally, therefore decreasing the number of actions the players can perform, decreasing server load.

TiDi is bad because it allows players who are not in the besieged system to converge there. Let's say a titan is tackled by a fleet that can destroy it in 5 minutes. Only those within 5 minutes of travel time can arrive, increasing the burden of the server. However a 10% TiDi would allow everyone within 50 minutes range to arrive, making sure the system is full off observers, killmail whores and such, making the battle unplayable for those who are actually involved. Besides increasing the server load, TiDi also changes the outcome, favoring the side with larger reinforcements, practically removing large scale surprise attacks from the game.

I don't even mention the "Captain Obvious" solution: stronger servers, as they are obviously expensive. Keeping every constellation 24/7 on a server which can support an Asakai sized battle is a huge waste of money. Refusing this solution however accepts that the server can't serve everyone, in the crucial moments, leading to TiDi and the problems above.

My solution would be selective service: when TiDi reaches 75%, the system goes to "yellow mode". In "Yellow mode" frigate sized ships, shuttles, noobships, destroyers and pods can't enter the system, nor they can undock from a station inside the system. Also, those of them who are not already in combat (PvP flagged, targeting or targeted by someone PvP flagged) are logged off. When the player tries to relog or undock in such a ship, he is offered the same window we see in Jita: that offers him to magically transported to a nearby system. Fleets would be granted 1 protected slot for every 10 ships that are not "yellow-banned" themselves, so a full fleet can have 24 tacklers, warpins, cynos that can operate under yellow mode. The technical way would be a protection priority list that the FC sets and the first N ships get protection.

Yellow mode would also force drone grouping: Drones of the same type of the same ship would fly to the same spot forming a "drone group" which is a single drone for the server with corresponding damage increase (so you'd control 1 fighter-bomber that does 20x damage instead of 20 FBs). These grouped drones would have two HP bars, one for single target damage, one for smartbomb. If the single target HP reaches zero, the group becomes smaller with full HP and targeting on this group has 1/N chance to break, representing the chance that your targeted drone died (if you had a 20x FB group and a ship killed one, you have a 19x FB group and he has 1/20 chance to be forced to retarget). If smartbomb HP reaches zero, the whole group dies.

The point is to remove the ships that are likely have little to none effect, letting those who actually affecting it operate with minimal TiDi. If TiDi disappears for 5 minutes, yellow mode is cancelled.

If yellow mode is not enough and TiDi is still below 75% for 5 minutes, "orange mode" is invoked. In this mode "yellow-banned" ships are disconnected and immediately disappear from space even if they were in combat, and T1 cruisers can't enter, undock or remain unless already in combat. The protected spots for small vessels is both recalculated (you can't get a spot after T1 cruisers) and decreased to 1/15 (16 small ships for a 255 man fleet). In orange mode subcapitals can only control 1 drone group, capitals 2, supercarriers 4. So if a subcap loses 2 drones (his drone group is down to 3 members), he can't send out a second group, must recall his group and resend it full.

If even orange mode fails and TiDi is still below 75% for more than 5 minutes, red mode is invoked. In red mode everything is instantly logged off and disappearing from space except capitals, battleships, strategic cruisers, logistics, dictors and command ships. Protected positions are recalculated and decreased to 1/20. All ships are limited to 1 drone group/ship and only heavy drones, sentries, fighters and FBs can be used.

This way the server could continue to operate without heavy TiDi with little change of the event. A single black-screened titan or the fact that a dread fleet arrived from the other end of the galaxy has larger effect on the outcome than removing 500 frigates and T1 cruisers, so it's just logical to keep the battlefield clear of litter.

Please spare me from the "everyone has the right to be there" comments. The TiDi is there because the server cannot serve everyone. We can only decide who should be not served.

PS: spare me from comments that point out that this or that speciality ship (like bombers) are important. Yes, I'm bad with PvP ships, so my example list is bad. But other people are good. The point of the post is to make these people a priority list of ships and as the server can't handle the load, kick out the low priority ships.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in Random | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Suffer mortals, as your pathetic password betrays you!
    One of the things we often don't put much thought into is password selection. Usually it is a loved-one's name or an easily remembe...
  • (I'm not) defining lowsec
    This is a rather short post, will be one more today, about my very first PvP action. Sugar reminded me of a problem that I read about a l...
  • The big EVE trick
    What is an easy game: where everyone can achieve what he wants easily. What is a hard game: where you can only advance by becoming better an...
  • You must station trade what you haul
    Well, actually you don't if you are fine with hauling for buy orders. This case you lose serious profit. If you are the station trader o...
  • The (total lack of) balance of trade of highsec
    The fact that you can be much more rich in highsec than in the competitive areas of EVE (low, null, WH) is one of my main messages. It can b...
  • Thinking about highsec POCOs
    In the next EVE patch, Rubicon, highsec customs offices will be capturable by players (actually you destroy and build your own, but it's...
  • What would happen if people could trade?
    The question of mirror-ability of strategies often comes up when I post my trading strategy. The 0.01 strategy is clearly mirror-able. If th...
  • October ganking report
    October was a great month for my corporation , We Gank Because We Care. You can see the results on the killboard but since October was 31 d...
  • The proper profit metric
    Live moron of the weekend post . Did they spent the last month under a rock? People having trouble making ISK with trading. Some rather go m...
  • ur a kid!
    The title is a troll comment I get often. It doesn't make much sense. It's clearly not an argument. While we know that socials don...

Categories

  • account
  • account theft
  • adobe
  • alpha
  • arena tournament
  • authenticator
  • authenticators
  • battle.net
  • beta
  • blizzard
  • brute force
  • cataclysm
  • diablo 3 phishing scam
  • dictionary attack
  • drive-by
  • email
  • fake
  • flash
  • game
  • Gold
  • guild
  • gumblar
  • hacked
  • hacking
  • hacks
  • Ideas
  • ISK
  • keylogger
  • march
  • mmo-champion
  • New
  • password
  • password stealing
  • patching
  • phishing
  • raiding
  • Random
  • ranks
  • remote auction house
  • scam
  • scams
  • security
  • security checklist
  • soccer
  • strong password
  • trojan
  • vulnerability
  • warcraft
  • wow
  • wowarmory
  • wowmatrix

Blog Archive

  • ▼  2013 (242)
    • ►  November (15)
    • ►  October (25)
    • ►  September (24)
    • ►  August (21)
    • ►  July (24)
    • ►  June (22)
    • ►  May (22)
    • ►  April (22)
    • ▼  March (20)
      • Low maintenance, high income PI
      • Business Thursday: my planet farmed it for free
      • Handling server overload
      • Brutal beat down of underskilled newbies and other...
      • Silver bullet: how could CCP bring back solo and s...
      • The scam of James 315
      • Business Thursday: less logins for pilots in training
      • I go to a bar to have fun, not to talk, dance or d...
      • The myth of the "highsec carebear"
      • Roleplaying an idiot
      • Nerfing highsec income doesn't hurt highsec casuals
      • Business Thursday: Blinged Tengu taking gates and ...
      • Moar l33t PvP: solo capital kill
      • API Coincidence detection against botters and a qu...
      • TEST expansion, best expansion
      • The meaning of "playing for fun"
      • Business Thursday: industrials and their rebalancing
      • "Your trading reports are fakes!"
      • I'm a carebear and I'm not happy about it
      • Elite PvP: Cormorant kills 3 Taloses
    • ►  February (21)
    • ►  January (26)
  • ►  2012 (261)
    • ►  December (24)
    • ►  November (21)
    • ►  October (24)
    • ►  September (21)
    • ►  August (26)
    • ►  July (25)
    • ►  June (20)
    • ►  May (25)
    • ►  April (23)
    • ►  March (23)
    • ►  February (23)
    • ►  January (6)
  • ►  2011 (4)
    • ►  September (1)
    • ►  April (1)
    • ►  March (1)
    • ►  January (1)
  • ►  2010 (17)
    • ►  November (1)
    • ►  September (2)
    • ►  August (1)
    • ►  July (1)
    • ►  June (2)
    • ►  May (2)
    • ►  April (1)
    • ►  March (2)
    • ►  February (2)
    • ►  January (3)
  • ►  2009 (4)
    • ►  December (1)
    • ►  October (1)
    • ►  September (1)
    • ►  July (1)
Powered by Blogger.

About Me

Unknown
View my complete profile