At three o'clock in the morning that day, the technical support cell phone was knocked out - not because of the attack, but because the players collectively complained about the card into the PPT. the boss directly in the group dumped a screenshot of the backstage delay: \"again can't get it done, the whole staff go to the Xinjiang computer room as a network administrator!<\/p>\n
People in the chess industry know that the high defense CDN thing is like wearing a bulletproof vest for the server, but the vest is too heavy for the user to run. I've seen too many teams spend money to buy terabytes of protection, and as a result, players directly uninstall the game because of slow loading. Speed and protection is not at all a single choice, the key to see how you tune the CDN.<\/p>\n
The speed bottleneck is never in the bandwidth, it's in the \"invisible routes\".<\/strong>The first time we troubleshooted a Southeast Asian user jam, we found that the traffic was actually detoured to the United States before returning to the source. One time we troubleshooted Southeast Asian users, and found that the traffic actually bypassed the United States before returning to the source. Later, we used traceroute to grab packets and realized that a CDN vendor's \"intelligent routing\" is simply artificial retardation - the node is obviously in Hong Kong, but the routing table points to Europe.<\/p>\n Let's start with a counterintuitive conclusion:High number of nodes does not equal speed<\/strong>. Some vendors boast 500+ nodes worldwide, but the edge nodes may be full of VMs to make up the numbers. I have tested CDN5 and CDN07 nodes in the same region, the same Tokyo server room, CDN5 latency is stable at 80ms, CDN07 fluctuations to 200ms+. Later unpacking found that the node of CDN07 is shared bandwidth, the evening peak directly by the next live platform to grab all the resources.<\/p>\n True 'proximity access' must satisfy three layers of matching:Physical distance \u2192 network hierarchy \u2192 service characteristics<\/strong>.. Chess traffic is typically small packet high frequency, the exact opposite of video large packet transfers. If you just apply a generic CDN, the TCP window tuning is all wrong.<\/p>\n This is a routing optimization solution we did for a Texas Hold'em platform:<\/p>\n Algorithms alone are not enough, they must be supported by real data. We have built a global ping monitoring network to test the quality of each node to the three major carriers every five minutes. Don't look at this job is simple, last year because of the backbone network jitter did not find an operator in time, lost 20% of daily activity.<\/p>\n Caching Strategy is the Nuke of Speed Optimization<\/strong>. But 90% people simply can't set the right caching rules -- either the dynamic interface is cached, resulting in the data being misplaced, or what should be cached is not cached. I've seen the most outrageous case: a platform cached the \/user\/info interface for an hour, and the player won gold and refreshed the page only to find that it was emptied...<\/p>\n Chess resources are to be cached in three levels:<\/p>\n The cache configuration in practice can be written like this:<\/p>\n Don't forget the client-side caching strategy! We had turned on Brotli compression on 08Host's node, and the js file volume alone was reduced by 70%, and the loading time dropped directly from 4s to 1.2s.<\/p>\n TCP protocol tuning is the hidden buff.<\/strong>. Most CDN vendors use default TCP parameters that are simply not suitable for chess scenarios. For example:<\/p>\n Once a customer insisted on using a major international CDN, but the player is always disconnected and reconnected. Later, the packet capture found that the TCP timeout parameter is too aggressive, 20% packet loss on disconnection. After changing to adaptive retransmission, the packet loss tolerance was raised to 35%, and the experience was immediately smooth.<\/p>\n Talk about having to spit:Even CDNs need to be \"teammate-proof\" these days.<\/strong>. Some vendors will dispatch your traffic to cheap server rooms in order to reduce costs. We have encountered the tiresome operation of \"Beijing users \u2192 Tianjin node \u2192 Heilongjiang source station\", and later directly wrote \"prohibit inter-provincial scheduling\" in the contract.<\/p>\n Now talk about the specific vendors to choose. CDN5's intelligent routing is really reliable, especially for Southeast Asia line optimization in place, but the price is two times the ordinary CDN. CDN07's caching performance is amazing, once carried a star endorsement of a hundred times the traffic impact. 08Host cost-effective the highest, the domestic node coverage to the third-tier cities, suitable for teams with limited budget.<\/p>\n Finally, I'll give a storm theory:Optimization without monitoring is metaphysics<\/strong>. An all-link monitoring system must be established:<\/p>\n Our self-developed monitoring board is directly connected to the alarm system, and any node delay exceeding the threshold will be automatically switched. There was a time when a fiber optic cable broke somewhere, and before the user could give feedback, the traffic had already been dispatched to the backup node.<\/p>\n Speed optimization is an eternal topic. Just last week replacing TCP with the QUIC protocol lowered latency by another 151 TP3T. but technology is always just a means to an end.What really matters is the ultimate pursuit of user experience<\/strong>--After all, players don't care how much technology you use, they just want to grab landlords and play mahjong smoothly.<\/p>\n (After writing this and looking at the big monitoring screen, the global node latency is all green at the moment, so I can finally get a full night's sleep - until the next hacking attack starts.)<\/p>","protected":false},"excerpt":{"rendered":" At three o'clock in the morning of that day, the technical support cell phone was busted - not because of the attack, but because the players collectively complained about the card into the PPT. the boss directly in the group dumped a screenshot of the delay in the background: \"again can't get it, all the staff go to the Xinjiang server room to be a network administrator! People in the chess industry know that the high defense CDN thing is like wearing a bulletproof vest for the server, but the vest is too heavy for the user to run. I've seen too many teams spend money to buy terabyte-level protection, and as a result, players directly uninstall the game because of slow loading. Speed and protection is not an optional question at all, the key depends on how you teach CDN. Speed bottleneck is never in the bandwidth, but in the \"invisible route\". One time when we investigated Southeast Asian users' congestion, we found that the traffic actually bypassed the U.S. before returning to the source. Later, we used traceroute to grab packets and realized that a CDN vendor's<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"gallery","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","footnotes":""},"categories":[150],"tags":[],"collection":[],"class_list":["post-976","post","type-post","status-publish","format-gallery","hentry","category-updates","post_format-post-format-gallery"],"_links":{"self":[{"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/posts\/976","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/comments?post=976"}],"version-history":[{"count":1,"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/posts\/976\/revisions"}],"predecessor-version":[{"id":1149,"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/posts\/976\/revisions\/1149"}],"wp:attachment":[{"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/media?parent=976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/categories?post=976"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/tags?post=976"},{"taxonomy":"collection","embeddable":true,"href":"https:\/\/www.ddosgj.com\/en\/wp-json\/wp\/v2\/collection?post=976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}