<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>暖池 on PlumePHP</title><link>https://plumephp.com/tags/%E6%9A%96%E6%B1%A0/</link><description>Recent content in 暖池 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Mon, 14 Jun 2021 08:52:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E6%9A%96%E6%B1%A0/index.xml" rel="self" type="application/rss+xml"/><item><title>副本实例暖池架构：高峰期开房不应该从零开始</title><link>https://plumephp.com/game-server-instance-warm-pool-architecture/</link><pubDate>Mon, 14 Jun 2021 08:52:00 +0800</pubDate><guid>https://plumephp.com/game-server-instance-warm-pool-architecture/</guid><description>&lt;h2 id="背景一个小功能背后往往有多条状态链"&gt;背景：一个小功能背后往往有多条状态链&lt;/h2&gt;
&lt;p&gt;活动刚开、晚高峰排位、主播带队副本时，玩家最直观的体验是“点开始后多久能进房间”。如果每个房间都从进程启动、地图加载、脚本初始化、配置拉取开始做，几百个并发开房请求会把启动链路打满。实例暖池要解决的是提前准备一批可用容器或房间进程。&lt;/p&gt;</description></item></channel></rss>