--.--.-- *--

スポンサーサイト

上記の広告は1ヶ月以上更新のないブログに表示されています。
新しい記事を書く事で広告が消せます。
--:--EDIT

2011.02.15 *Tue

Latency Changes in Patch 4.0.6

適切な情報開示が求められる昨今なのに、自分が何したって話をすっかり書かなくなった気がするsynakoです、こんばんは。

自分用に気になる記事とかネタとかまとめておく作業を始めて以来、日記的要素が二の次になってしまった感がある・・・

たまには面白かったと思える事でも書いてみよう!


2011/2/13
今日はNefarianのP2の60%のビリビリ前に担当してたAddが死んじゃって、「Atk止めてって言ったのに!Feintできねえぞゴルァ!」なんて脳内で悪態をついてる間に自分のHPが半分以下まで減ってしまい、ここで使わずにいつ使うって場面なのにHSとPot使うのケチってビリビリで死んじゃいました。
その後P3は私抜きで順調に進んでいったけど、Nefの残りHP3%でDPSが足りずにWipeしてしまい、「Baby Wipeだな!」って言われてしまった(ウワアァン
結局その日はその3%が最高で、Nefarian Killは来週以降に持ち越された・・・
今日の反省点: 短気は損気、スイマセンスイマセンスイマセン


ダメだ、面白いネタを考えようとすると、なぜか自虐ネタに走る傾向は相変わらずだ・・・

なーんて超脱線してますが、今回は4.0.6で表示が2つに分かれたLatencyに関するニュースの紹介です。

元記事はMMO-Champよりこちら。


Latency Changes in Patch 4.0.6

Home/World latency in Patch 4.0.6
Patch 4.0.6 changed how latency is displayed to the client, we now have a "Home" latency and a "World" latency, BrianI on the Tech Support forums posted a long explanation of what it means exactly and how latency works in WoW.


Originally Posted by BrianI (Source)
We have been seeing a lot of confusion regarding some of our recent changes to the User Interface, specifically in regard to the new in-game latency meters. With 4.0.6, we have split the two separate connections the client forms to our game servers into two different ratings, labeled 'Home' and 'World'.

The speculation regarding what these ratings mean has been very interesting and some of the guesses as to what the numbers actually refer to have been pretty imaginative. Some have speculated that 'Home' referred to your personal latency and 'World' was Blizzard's latency. This is incorrect.

In essence,
'Home' refers to your connection to your realm server. This connection sends chat data, auction house stuff, guild chat and info, some addon data, and various other data. It is a pretty slim connection in terms of bandwidth requirements.

'World' is a reference to the connection to our servers that transmits all the other data... combat, data from the people around you (specs, gear, enchants, etc.), NPCs, mobs, casting, professions, etc. Going into a highly populated zone (like a capital city) will drastically increase the amount of data being sent over this connection and will raise the reported latency.

Prior to 4.0.6, the in-game latency monitor only showed 'World' latency, which caused a lot of confusion for people who had no lag while chatting, but couldn't cast or interact with NPCs and ended up getting kicked offline. We hoped that including the latency meters for both connections would assist in clarifying this for everyone.

As is probably obvious based upon this information, the two connections are not used equally. There is a much larger amount of data being sent over the World connection, which is a good reason you may see disparities between the two times. If there is a large chunk of data 'queued' up on the server and waiting to be sent to your client, that 'ping' to the server is going to have to wait its turn in line, and the actual number returned will be much higher than the 'Home' connection.

"Well, great," you may say, "but what does that mean to me?!"

Not much, maybe, but I wanted to focus on how local (or network) factors can (and will!) affect these numbers.

Here are the most common causes of high pings/latency (on both Home and World):
  • 1) Wireless
  • 2) Packet loss
  • 3) Almost-but-not-quite-broadband*
  • 4) Addons (yes, those wonderful UI modifications)
  • 5) Firewalls (some firewalls do interesting things to latency... try playing without it to see if it helps!)
  • 5) Mis-configured or defective home routers (please temporarily bypass before anything else)
  • 6) Quality of Service and Traffic Management Systems performing packet queuing of some sort.
  • 7) Net link saturation (not necessarily your ISP, but somewhere between you and Blizzard)

*As of July 2010, the 'official' definition of Broadband Internet (per the FCC) is '4Mbps downstream and 1Mbps upstream'. Anything lower than this is not 'officially' broadband.

Lowering video settings (especially view distance) has the added benefit of lowering the amount of data your connection is asked to convey, as well, so even that can be a valid troubleshooting step.

If your 'Home' connection latency is low and your 'World' connection latency is high, that frequently indicates that there is some sort of QoS congestion controls being applied to your internet connection, at either the micro (LAN) or macro (WAN) level. A common symptom would be that you would be able to chat, but not to cast.

If both connections report high latency, that means your connection to our servers, in general, is almost completely saturated, or 'overflowing'. Without making any claims where that saturation lies, that seems to have been the most common case to date.

Please refer to our support pages (such as
http://us.blizzard.com/support/artic...ategoryId=2329) or contact a technical support representative directly for further information and troubleshooting.




Patch 4.0.6 Latency Changes
BrianI also explained why some people saw their latency improve dramatically in 4.0.6, and how they had to revert the changes for the moment to keep everyone happy. The good news is: tons of improvements are coming!
Originally Posted by BrianI (Source)
With 4.0.6 we made a couple changes to our instance servers in an attempt to lower latency. Unfortunately, with those changes came increased bandwidth requirements. Due to the nature of the feedback we received, we have temporarily reverted those changes, as of around ~6pm PST last night. Are you still experiencing issues?

Could you go into a little more detail on this? You said the change done with 4.0.6 caused a bandwidth problem but was said problem on my end, your end, or somewhere in between? If this change did cause a problem on my end how can I prepare for when it has been reimplemented?

In a nutshell? That's a bit hard to explain clearly, but I'll try. Some people have an ISP whose peering link to their tier 1 backbone provider is oversaturated. Some people have ISPs that are throttling their connection in some way. Some people are on wireless connections, or are using old routers that are causing issues. Some people simply have a misconfigured or malfunctioning LAN device. Some people just have lower bandwidth connections. I’ll explain further below.

Unequivocally, the bandwidth problems were not internal to our network. We never came close to capacity. The actual total peak transfer data rate was around 1/5th of our maximum capacity.

When we performed maintenance the day we released 4.0.6 we made a couple modifications to our instance (BG/arena/dungeon/raid) servers. One of these changes had the effect of lowering latency for a very high percentage of our users... around 99% or so. The numbers were pretty staggering, to be honest. My personal ‘instance server’ experience was a drop from 120-150ms average ping down to 12ms. No, really, 12 ms. From my home residential connection. It was amazing. Raiding was glorious. The vast majority of our users saw similar improvements.

Then again, I have a very stable high bandwidth cable connection with a well designed internal LAN, and I had no problems handling the requisite increases in bandwidth. You see, part of that reason the latency went down is that a lot more packets were being sent. In some cases, the bandwidth almost tripled. For those who don't (or can't) meet all of our minimum system requirements (e.g. broadband internet*) or who are having issues with their connection or are on a flaky wireless connection... things weren't so pretty. We ended up rolling back that change until a later date when we will be able to selectively turn on that performance enhancement on a ‘per client’ basis. Unfortunately, that will require another patch, so we’ll just have to wait a bit.

Yes, we really did roll back that change for something that negatively affected less than 1% of total users. We really do care about providing the best environment we can. We do things like this frequently.

We do understand that some people do not have the options available to them that others do. We know that people are playing on 6 to 8 year old computers (in some cases, even older) with a flaky 3G or satellite connection, even though this does not meet our minimum system requirements. Not everyone can afford newer or better and not all areas have a faster connection available, currently. We do see people connecting from all over the world from backbones that are throttling their connections due to the cost of transmitting data over transoceanic cables. We see all these things… and we feel some of the same frustrations these people do when trying to have a smooth gaming experience. It is actually difficult to be unable to help someone due to situations outside your control.

To be honest, World of Warcraft was not designed for these types of setups. That is why we are very clear with our ‘minimum system requirements’ and what, exactly, is supported. Will we still try to help you connect and do our best to help you out, anyway? Absolutely. We just can’t make any promises or guarantees, as much as we would like to. The actual bandwidth requirements are not that high. In ordinary play, WoW shouldn’t end up taking more than a few hundred megabytes a month. What is important, however, is the stability of the connection and width of the ‘pipe’, due to the bursts of data that need to be transmitted at times. While total bandwidth may not be high, there will be short periods where a ton of data is being sent simultaneously (like, you know, raid boss fights or even when first logging on to a server when your toon is in a capital city).

We may wish it were otherwise, but if we tried to send and receive less data we wouldn’t be able to provide the immersive, complex, top-notch gaming experience (most people) have come to know, love, and expect from Blizzard Entertainment. I wish there were some way to do both, but there really isn’t, at least with today’s technologies. Either we can provide an intense environment that over 98% of people who play WoW have no problems with, or we can lower our standards to unacceptable levels and try to get that extra ~2% in, as well.

Anyway, I apologize for the lengthy post, and I’m sure this will be lost in the thread, but I’ve been meaning to post some thoughts on this for awhile. I hope you’ve enjoyed the read… it was fun to type, at least.

元々Chat等とゲームの主データを扱う部分は分かれていて、Lagを感じるときでもChatは平気とかだったと思います。
4.0.6ではそのGapの正体が目に見えた感じで、HomeとWorldのLatencyが表示されるようになりました。

各Latencyはこんなとこに絡んでいるようです。

Home: ChatやAHやいくつかのAddonで扱うデータ等を、各Realm鯖とやりとりする接続速度
World: 上記以外の全データ(戦闘・自分の周りのPC(装備やEnchantも含む)・NPC・Mob・Cast・Profession・その他諸々)をHomeとは別のサーバ群とやりとりする接続速度(首都等の人が混み合う場所だと劇的にデータ量が増加するためこちらのLatencyは上昇しがち)

このWorld Latencyを上げる要因が1)~7)で紹介されてますが・・・
それ以前に日本からだと経路の関係上、良くても140ms前後に落ち着く事が多いようです。

やばい、脱線仕掛けてる気がする・・・


また、4.0.6以降Latencyがかなり改善してる人がいたら、それは2つめのニュースによるものかもしれません。

とにかく、BlizがLatencyを気にして改善に注力してくれるのは嬉しいことだぁ^^


20:15CM(0)TB(0)EDIT

COMMENT

Comment Form


秘密にする
 

TRACKBACK

TrackBack List



プロフィール

synako

Author:synako
World of Warcraft
Proudmoore/Ally
Guild:Divine Wind
Babysynaps(Rog)
Babysynako(DK)
Babygilfy(Hnt)
Babyegg(Shm)
Babybaby(Pal)
Babybabe(Mag)
Babymoussy(Pri)
Babyvivian(Wlk)
Babymcbee(War)
Babyciuciu(Dru)



最新記事



最新コメント



月別アーカイブ



カテゴリ



リンク

このブログをリンクに追加する



検索フォーム



RSSリンクの表示



ブロとも申請フォーム

この人とブロともになる



QRコード

QR



FC2カウンター



Copyright © 品子って・・・ All Rights Reserved.
テンプレート配布者: サリイ  素材:Bee   ・・・ 
上記広告は1ヶ月以上更新のないブログに表示されています。新しい記事を書くことで広告を消せます。