可量化的优化。绝不破坏你的服务器。当出现卡顿——你就能知道原因。
大多数“优化”插件要么重复 Paper 已经具备的设置,要么通过关闭游戏来节省 CPU。TickWarden 会向你展示卡顿的实际来源,记录每次卡顿发生时的世界状态快照,告诉你哪些设置可以修复问题,并处理配置文件无法处理的情况。免费,无需依赖项,无遥测数据。一个 jar 包支持 Paper、Purpur 和 Folia,适用于 1.21.4 - 1.21.11 和 26.x 版本。
常规手段
卡顿插件往往以玩家最先察觉的方式节省 CPU:
- 当 TPS 下降时取消所有生物生成——包括繁殖箱和刷怪笼
- 在高负载下关闭红石,停止漏斗和水流流动
- 重写
randomTickSpeed 等游戏规则,这些更改会保留在你的世界存档中
- 实施每区块投射物限制,一旦地上有几支箭就会导致弓无法使用
- 按计时器删除生物和物品,包括农场
- 通过服务端内部机制替换生物 AI,这会在每次 Minecraft 更新时导致崩溃
- 重新实现 Paper 已经作为单行配置提供的选项
- 默认发送遥测数据和性能分析器数据回传至作者服务器
TickWarden 不做上述任何操作。
TickWarden 的不同之处
- 仅使用 Paper API。 无 NMS(非公开方法),无反射。Minecraft 更新不会导致其失效——同一个 jar 包可在 1.21.4 和 26.2 上运行。
- 不向你的世界写入任何内容。 移除插件后,服务器与之前完全一致。它唯一动态更改的设置——严重卡顿下的模拟距离——会通知管理员,自动恢复且永不写入磁盘。
- 效果可见。
/tickwarden report 显示 tick 时间和每个模块的执行情况。
- 无网络请求。 无遥测数据,无更新检查器。它唯一可能发出的请求是 Discord Webhook ——前提是你自己设置了它。
卡顿事件日志 —— “为什么卡顿了?”
“昨晚服务器卡顿了”这句话如果没有具体位置信息毫无用处。当服务器停滞时,TickWarden 会截取该时刻的世界快照并保存:
- 最拥挤的区块以及站在它们旁边的玩家
- 正在生成的新区块及其附近是否有玩家——滑翔翼飞入新地形是最常见的原因之一
- 红石活动和运行的时钟
- 在线玩家数量、各世界的实体数和区块数
然后用通俗语言指出可能的原因:“史蒂夫附近生成了 139 个新区块”、“世界 120, -40 的拥挤区块:1400 个实体,主要是鸡”、“红石——每秒 48000 次更新,最繁忙的世界 60, 60(一个永不停止的时钟)”。如果世界中没有任何异常,它会诚实地说明这一点,并建议你使用 spark ——来自插件的卡顿是世界快照无法检测到的。
- 由相同原因引起的一系列峰值算作一次事件,而不是四十行的垃圾信息。
- 在线管理员在事件开始时收到聊天消息——点击可查看详情,点击区块可传送至该处。
/tickwarden incidents 列出自启动以来的所有事件,/tickwarden incident <n> 显示单个事件的完整详情。
- 每个事件都会写入
plugins/TickWarden/incidents/<date>.log,旧文件在 14 天后清理。
- 可选:每个完成的事件会被发布到指定的 Discord 频道。
每次快照的成本约为每 1000 个实体 1 毫秒,且仅在每次事件中拍摄一次,而非每个 tick。
Tick 监控器 —— /tickwarden report
过去 10 秒、1 分钟、5 分钟和 15 分钟内的平均、第 95 百分位和最差 tick 时间,以及每个窗口的实际 TPS。下方显示卡顿峰值、事件列表以及自启动以来每个模块的操作情况,从而让“一分钟前卡顿了”变成每次更改后可比较的具体数值。
卡顿扫描器 —— /tickwarden scan
拥有最多实体、最多方块实体(漏斗、箱子、熔炉)和红石的区块,并按类型细分——“93: 60 只鸡,33 个物品”。点击一行即可传送至该处。只读模式:它只显示你需要查看的位置,绝不会决定哪个农场必须被拆除。
红石监测
一个遗留在基地角落未关闭的时钟会让服务器日夜忙碌,即使其主人早已不再关心。TickWarden 统计每个区块中的红石信号变化和活塞移动次数。如果一个区块几乎每秒都处于繁忙状态持续 30 秒,则判定为时钟——它会在 /tickwarden scan 中显示“连续运行 2 小时 14 分钟”,并出现在卡顿事件中。
由时钟驱动的农场(海带、竹子)也会显示出来,这是有意为之:先观察,再决定。如果你愿意,TickWarden 可以拆除连续运行超过 10 分钟的时钟——最繁忙的中继器、比较器或侦测器会掉落为物品,并通知管理员其位置。此选项默认关闭:因为它会破坏玩家的建筑。
实测:640 个侦测器时钟(每秒 49000 次更新)——监测它们的成本在测量噪声中微不足道。
自适应模拟距离
当服务器持续落后——平均 tick 超过 50 毫秒持续 20 秒时——玩家周围的区块 tick 半径缩小:逐步降低,如果还不够则继续降低,但最低不低于 5。当负载下降时,距离每分钟逐步恢复一级。管理员会收到双向变化的聊天消息。
玩家看到的与世界保持不变——视距不受影响——但处于半径边缘的作物、生物和农场会暂停,直到距离恢复。单次长时间冻结(如世界保存)不计入——仅计算持续的卡顿。不会向 server.properties 或世界文件写入任何内容:重启或执行 /tickwarden reload 后,距离恢复为你原来的设置。如果你更倾向于让服务器直接卡顿,只需一行配置即可关闭此功能。
配置顾问 —— /tickwarden advise
在 Paper 上,最大的性能提升来自其配置,而非插件。顾问会读取 server.properties、bukkit.yml、spigot.yml 以及两份 Paper 配置文件,并执行 38 项检查:模拟距离、实体激活与追踪范围、实体碰撞、生成限制、消失范围、红石实现、漏斗事件、村民传感器、藏宝图搜索、区块保存限制等。
每条建议都包含三部分内容:该设置对服务器的开销、建议的值,以及玩家能注意到的变化——让你明明白白地做决定。在聊天中悬停某一行即可查看解释。它绝不会修改你的文件:Paper 的配置文件中充满了注释,而且无论如何更改都需要重启服务器。
系统会检测并报告 paper-world.yml 中的按世界覆盖设置。所有检查均针对每个受支持版本的默认配置进行验证;如果你的 Paper 版本中不存在某项检查,则跳过该项,绝不猜测。
影响评级基于实测数据,而非民间传说。将 max-entity-collisions 从 8 降至 2(这是各类优化指南的最爱),在拥挤式围栏(3×3 方块内关押 40 只动物)中减少了约 10% 的刻时间,而在有充足空间的普通围栏中毫无影响。因此,顾问将其评为中等影响,并明确指出它在何处有效。
群体控制
在一个有六十头牛的围栏里,每一头牛都会选择一个随机位置、寻路前往并推开邻居——这些行为虽然不可见,但每刻都要付出代价。当某个区块拥有 16 只或更多农场动物时,TickWarden 会让它们静止不动。
所有重要功能仍像原版一样正常工作,因为它是通过 Paper 自身的生物目标 API 实现的:繁殖、跟随手持食物的玩家、受伤时惊慌、在水中漂浮、被剪毛的绵羊吃草以重新长出羊毛。幼崽和宠物永远不会受到影响。此目标不会保存到世界中——重启服务器或移除插件后,动物行为将恢复如初。
在测试服务器上测量(16 个密集围栏中共 960 只动物,动物活跃度如同玩家站在旁边,每种情况交替运行三次,每次 60 秒):
|
平均刻时间 |
| 群体控制关闭 |
8.75 ms |
| 群体控制开启 |
7.17 ms |
这占该服务器总刻时间的 18%,约占游荡动物所耗时间的 60%。在 1.21.4 - 26.1.2 版本中,同一测试结果为 14-21%。我们还验证了以下行为:可繁殖的动物产下了小牛,受伤的动物逃跑,被剪毛的绵羊重新长出羊毛,定居的牛和羊转身跟随手持小麦的玩家。
它仅对靠近玩家的围栏有意义——原版会在没有任何玩家在 32 格范围内时阻止动物游荡。但这恰恰是玩家所在的位置:就在他们的农场旁边。
繁殖上限
生存服务器上最大的实体延迟通常不是怪物造成的,而是某人喂了几个月的麦子的围栏。当 16 格半径内已有 64 只同种动物(鸡为 96 只)时,繁殖和投掷鸡蛋都不会产生幼崽——而喂食的玩家会在动作栏中看到原因,用的是他们自己的语言,而不是报告一个 bug。
Folia
同一个 jar 包可在 Folia 上运行——启用所有模块,而非精简模式。Folia 没有单一的全局刻:区域并行 ticking,每个区域在自己的线程上运行。因此,TickWarden 在 Paper 上测量的“每服务器”内容,在 Folia 上是按区域测量的:
/tickwarden report 显示所有区域的刻时间汇总(平均值、p95、最差值、有多少区域落后于计划)以及一个区域表格——TPS、MSPT、所在世界及其中的玩家。落后严重的区域排在前面;点击其中一个即可传送过去。
- 延迟事件 指明导致延迟的区域,并仅统计这些区域内的实体和区块数量。多个区域同时出现尖峰被视为一个事件,并列出相关区域。全局区域(控制台、命令、时间与天气)落后也会被捕获。
/tickwarden scan 允许每个区域自行统计其区块。如果一个区域延迟严重到 5 秒内无响应,则会被排除——扫描结果会明确说明这一点。
- 自适应模拟距离 按区域决定:只有延迟区域的玩家会降低模拟距离,其他世界保持原样。离开该区域后,你的正常模拟距离在一秒内即可恢复。
- 红石监听 在区域线程上进行计数;如果时钟所在的区域线程卡顿,则该时钟被视为损坏。
- 占位符
tps 和 mspt 对应的是玩家所在区域的数值。
- 群体控制 和 繁殖上限 在 Folia 上的表现与 Paper 相同。
仍仅依赖 Paper API:无需 Folia 特定依赖,也不涉及服务器内部机制。已在 Folia 1.21.11 和 26.2 上测试,其中多个区域并行 ticking。
PlaceholderAPI
可选。安装 PlaceholderAPI 后,可将服务器健康状态显示记分板、TAB 列表或全息图上:
| 占位符 |
值 |
%tickwarden_tps% |
过去一分钟的 TPS(在 Folia 上为玩家所在区域的 TPS) |
%tickwarden_mspt% |
过去一分钟的平均刻时间,毫秒(在 Folia 上为玩家所在区域的值,基于 5 秒窗口) |
%tickwarden_mspt_color% |
同上,但带有颜色(绿色 / 黄色 / 红色) |
%tickwarden_incidents_today% |
自午夜以来的延迟事件数(重启后保留) |
%tickwarden_last_incident% |
距上次延迟事件结束的时间 |
%tickwarden_simdistance% |
当前模拟距离 |
%tickwarden_redstone_clocks% |
当前正在运行的红石时钟数量 |
在 26.x 版本中,请使用 PlaceholderAPI 2.12 或更高版本——旧版本无法在此启动。
命令
| 命令 |
功能 |
/tickwarden report |
刻时间、延迟尖峰、事件、各模块执行情况 |
/tickwarden incidents |
自启动以来的延迟事件 |
/tickwarden incident [n] |
完整展示某一事件:原因、拥挤区块、附近玩家 |
/tickwarden scan |
实体最多、方块实体和红石最多的区块 |
/tickwarden advise |
值得调整的设置(加上 all 参数也包含次要设置) |
/tickwarden reload |
无需重启即可应用配置更改 |
别名 /tw。权限:tickwarden.admin 用于执行命令,tickwarden.notify 用于接收关于卡顿事件、模拟距离和时钟故障的聊天消息。两者默认均为 OP(管理员)权限。
配置
incidents:
enabled: true
spike-ms: 150 # 单次持续如此长的 tick 将触发事件
sustained-mspt: 50 # ...同样,若 5 秒平均值达到此高度也会触发
notify-admins: true
discord-webhook: "" # 留空 = 关闭
keep-days: 14
redstone:
enabled: true
clock-seconds: 30
break-clocks: false
adaptive-distance:
enabled: true
lag-mspt: 50
min-distance: 5
crowd-control:
enabled: true
crowd-size: 16
entity-types: [COW, MOOSHROOM, SHEEP, PIG, CHICKEN]
breed-cap:
enabled: true
radius: 16
limit: 64
limits:
CHICKEN: 96
advisor:
language: en # 或 ru
ignore: [] # 你决定保留原样不进行检查的项目
配置文件中包含所有消息。英文和俄文版本会在首次启动时生成 config-ru.yml 文件并置于配置文件旁,其中包含对每条顾问检查项的俄语解释。
依赖要求
|
|
| 服务器端 |
Paper, Purpur 或 Folia 1.21.4 - 1.21.11, 26.1 - 26.2 |
| 已测试环境 |
Paper 1.21.4, 1.21.8, 1.21.11, 26.1.2, 26.2; Folia 1.21.11, 26.2 |
| Java 版本 |
21 或更高 |
| 依赖项 |
无;PlaceholderAPI 为可选 |
它不做什么
- 它不会删除实体、清理地面物品或按计时器杀死怪物。如果你需要这些功能,扫描器会告诉你手动操作的位置。
- 当 TPS 下降时,它不会触碰红石、刷怪机制或游戏规则。应对卡顿的唯一自动反应是调整模拟距离,且该调整会自动通知玩家并自行撤销。
- 它不是性能分析器(Profiler)。若要排查“哪个插件运行缓慢”,请使用 spark —— TickWarden 回答的是:“我的世界中负载在哪里?卡顿发生时发生了什么?我应该做出哪些更改?”
支持
欢迎提交错误报告,其优先级高于功能请求。提供你的配置文件、/tickwarden report 输出结果、/tickwarden incident 显示的事件记录以及相关日志行,此类报告将被最快修复。
Optimization you can measure. Nothing that breaks your server. And when it lags - you find out why.
Most "optimization" plugins either repeat settings Paper already has, or save CPU by switching the game off. TickWarden shows you where the lag actually is, keeps a journal of every lag incident with what was going on at that moment, tells you which settings fix it, and handles the things a config file cannot. Free, no required dependencies, no telemetry. One jar for Paper, Purpur and Folia, 1.21.4 - 1.21.11 and 26.x.
The usual tricks
Lag plugins tend to save CPU in ways players notice first:
- cancelling all mob spawning when TPS dips - breeding and spawners included
- switching redstone off, stopping hoppers and water flow under load
- rewriting gamerules such as
randomTickSpeed, which then stay in your world save
- per-chunk projectile limits that stop bows working once a few arrows lie on the ground
- deleting mobs and items on a timer, farms included
- replacing mob AI through server internals, which breaks with every Minecraft update
- re-implementing options Paper already ships as a single config line
- sending telemetry and profiler data home by default
TickWarden does none of these.
How TickWarden is different
- Paper API only. No NMS, no reflection. Nothing to break when Minecraft updates - the same jar runs on 1.21.4 and on 26.2.
- Nothing is saved into your worlds. Remove the plugin and the server is exactly as it was. The one setting it changes on the fly - simulation distance under heavy lag - is announced to admins, restored by itself and never written to disk.
- The effect is visible.
/tickwarden report shows tick times and what every module did.
- No network requests. No telemetry, no update checker. The only request it can ever make is a Discord webhook - if you set one yourself.
Lag incident journal - "why did it lag?"
"The server lagged last night" is useless without knowing where. When the server stalls, TickWarden takes a snapshot of the world at that moment and keeps it:
- the most crowded chunks and which player stood next to them
- new chunks being generated, and near whom - an elytra flight into fresh terrain is one of the most common causes
- redstone activity and running clocks
- players online, entities and chunks per world
Then it names the likely cause in plain words: "139 new chunks generated in world near Steve", "crowded chunk world 120, -40: 1400 entities, mostly Chicken", "redstone - 48000 updates a second, busiest world 60, 60 (a clock, never stops)". When nothing in the world stands out, it says so honestly and points you to spark - a lag from a plugin is not something a world snapshot can see.
- A run of spikes from the same cause is one incident, not forty lines of spam.
- Online admins get a chat message when an incident starts - click it for the details, click a chunk to teleport there.
/tickwarden incidents lists the incidents since start, /tickwarden incident <n> shows one in full.
- Every incident is written to
plugins/TickWarden/incidents/<date>.log, old files are cleaned up after 14 days.
- Optional: each finished incident is posted to a Discord channel.
A snapshot costs about 1 ms per 1000 entities and is taken once per incident, not every tick.
Tick monitor - /tickwarden report
Average, 95th percentile and worst tick over the last 10 seconds, 1, 5 and 15 minutes, with real TPS for each window. Below them - lag spikes, incidents and what every module did since start, so "it lagged a minute ago" becomes a number you can compare after every change.
Lag scanner - /tickwarden scan
The chunks with the most entities, the most block entities (hoppers, chests, furnaces) and the most redstone, with a breakdown by type - "93: 60 chickens, 33 items". Click a line to teleport there. Read-only: it shows you where to look and never decides whose farm has to go.
Redstone watch
A clock left running in a forgotten corner of a base keeps the server busy day and night, long after its owner stopped caring. TickWarden counts redstone signal changes and piston moves in every chunk. A chunk that stays busy nearly every second for 30 seconds is a clock - it shows up in /tickwarden scan with "nonstop for 2h 14m" and in lag incidents.
Farms driven by a clock (kelp, bamboo) show up too, on purpose: look first, then decide. If you want, TickWarden can break clocks that ran nonstop for 10 minutes - the busiest repeater, comparator or observer drops as an item and admins are told where. That option is off by default: it breaks players' builds.
Measured: 640 observer clocks (49 000 updates a second) - the cost of watching them is lost in measurement noise.
Adaptive simulation distance
When the server keeps falling behind - the average tick over 50 ms for 20 seconds - chunks around players tick in a smaller radius: one step down, then another if that was not enough, never below 5. When the load drops, the distance comes back one step a minute. Admins get a chat message each way.
Players see the world as before - view distance is not touched - but crops, mobs and farms at the edge of the radius pause until the distance is back. A single long freeze, such as a world save, does not count - only lag that lasts. Nothing is written to server.properties or the worlds: after a restart, or /tickwarden reload, the distance is your own again. Turn it off with one line if you prefer the server to just lag.
Config advisor - /tickwarden advise
The biggest performance gains on Paper come from its configuration, not from plugins. The advisor reads server.properties, bukkit.yml, spigot.yml and both Paper configs and runs 38 checks: simulation distance, entity activation and tracking ranges, entity collisions, spawn limits, despawn ranges, redstone implementation, hopper events, villager sensors, treasure map searches, chunk save limits and more.
Every recommendation says three things: what the setting costs the server, what to set it to, and what players will notice after the change - so you decide with your eyes open. Hover a line in chat for the explanation. It never edits your files: Paper's configs are full of comments, and the change needs a restart anyway.
Per-world overrides in paper-world.yml are detected and reported. Checks are verified against the default configs of every supported version; a check that does not exist in your Paper version is skipped, not guessed.
Impact ratings follow measurements, not folklore. Lowering max-entity-collisions from 8 to 2 - a favourite of every optimization guide - cut about 10% of the tick in cramming-style pens (40 animals in 3×3 blocks) and nothing at all in ordinary pens where animals have room. So the advisor rates it medium and says exactly where it helps.
Crowd control
In a pen with sixty cows every one of them keeps choosing a random spot, pathfinding to it and pushing its neighbours - none of it visible, all of it paid for every tick. When a chunk holds 16 or more farm animals, TickWarden makes them stand still instead.
Everything that matters still works exactly as in vanilla, because it is done with Paper's own mob goal API: breeding, following a player holding food, panicking when hit, floating in water, sheared sheep eating grass to regrow wool. Babies and pets are never touched. The goal is not saved to the world - restart or remove the plugin and the animals behave as before.
Measured on a test server (960 animals in 16 packed pens, animals active as if a player stood next to them, three alternating 60-second runs each way):
|
Average tick |
| Crowd control off |
8.75 ms |
| Crowd control on |
7.17 ms |
That is 18% of the whole tick on that server, and about 60% of what wandering animals cost. On 1.21.4 - 26.1.2 the same test gave 14-21%. We also verified with it on: animals set to breed produced calves, hit animals ran, sheared sheep regrew wool, and settled cows and sheep turned and followed a player holding wheat.
It only matters for pens near players - vanilla already stops animals wandering when nobody is within 32 blocks. But that is exactly where your players are: next to their farms.
Breed cap
The biggest entity lag on a survival server is rarely monsters. It is the pen someone has fed wheat for months. When there are already 64 animals of the same type within 16 blocks (96 for chickens), breeding and thrown eggs produce no babies - and the player feeding them sees why in the action bar, in their own language, instead of reporting a bug.
Folia
The same jar runs on Folia - with every module, not a cut-down mode. Folia has no single server tick: regions tick in parallel, each on its own thread. So everything TickWarden measures "per server" on Paper, it measures per region there:
/tickwarden report shows all region ticks together (average, p95, worst, how many ran behind schedule) and a table of regions - TPS, MSPT, where it is and which players are in it. Lagging regions come first; click one to teleport.
- Lag incidents name the region that lagged, and count entities and chunks in the lagging regions only. Spikes in several regions at once are one incident with the list of regions. The global region (console, commands, time and weather) falling behind is caught too.
/tickwarden scan lets every region count its own chunks. A region lagging so hard that it does not answer in 5 seconds is left out - and the scan says so.
- Adaptive simulation distance is decided per region: only the players of the lagging region get a lower distance, the worlds keep theirs. Leave that region and your normal distance is back within a second.
- Redstone watch counts on the region threads; a clock is broken on the thread of its own region.
- Placeholders
tps and mspt are of the player's own region.
- Crowd control and the breed cap work as on Paper.
Still Paper API only: no Folia-specific dependency and no server internals. Tested on Folia 1.21.11 and 26.2 with several regions ticking in parallel.
PlaceholderAPI
Optional. With PlaceholderAPI installed, put server health on a scoreboard, in TAB or on a hologram:
| Placeholder |
Value |
%tickwarden_tps% |
TPS over the last minute (on Folia - of the player's region) |
%tickwarden_mspt% |
Average tick over the last minute, ms (on Folia - of the player's region, over 5 s) |
%tickwarden_mspt_color% |
The same, colored green / yellow / red |
%tickwarden_incidents_today% |
Lag incidents since midnight (survives restarts) |
%tickwarden_last_incident% |
Time since the last lag incident ended |
%tickwarden_simdistance% |
Current simulation distance |
%tickwarden_redstone_clocks% |
Redstone clocks running now |
On 26.x use PlaceholderAPI 2.12 or newer - older versions do not start there.
Commands
| Command |
What it does |
/tickwarden report |
Tick times, lag spikes, incidents, what the modules did |
/tickwarden incidents |
Lag incidents since start |
/tickwarden incident [n] |
One incident in full: cause, crowded chunks, players nearby |
/tickwarden scan |
Chunks with the most entities, block entities and redstone |
/tickwarden advise |
Settings worth changing (all for minor ones too) |
/tickwarden reload |
Apply config changes without a restart |
Alias /tw. Permissions: tickwarden.admin - the commands, tickwarden.notify - chat messages about lag incidents, simulation distance and broken clocks. Both are op by default.
Configuration
incidents:
enabled: true
spike-ms: 150 # a single tick this long opens an incident
sustained-mspt: 50 # ...and so does a 5-second average this high
notify-admins: true
discord-webhook: "" # empty = off
keep-days: 14
redstone:
enabled: true
clock-seconds: 30
break-clocks: false
adaptive-distance:
enabled: true
lag-mspt: 50
min-distance: 5
crowd-control:
enabled: true
crowd-size: 16
entity-types: [COW, MOOSHROOM, SHEEP, PIG, CHICKEN]
breed-cap:
enabled: true
radius: 16
limit: 64
limits:
CHICKEN: 96
advisor:
language: en # or ru
ignore: [] # checks you decided to keep as they are
Every message is in the config. English and Russian - config-ru.yml lands next to your config on first start, including Russian explanations for every advisor check.
Requirements
|
|
| Server |
Paper, Purpur or Folia 1.21.4 - 1.21.11, 26.1 - 26.2 |
| Tested on |
Paper 1.21.4, 1.21.8, 1.21.11, 26.1.2, 26.2; Folia 1.21.11, 26.2 |
| Java |
21 or newer |
| Dependencies |
none; PlaceholderAPI optional |
What it does not do
- It does not delete entities, clear ground items or kill mobs on a timer. If you want that, the scanner shows you where to do it by hand.
- It does not touch redstone, spawning or gamerules when TPS drops. The only automatic reaction to lag is the simulation distance, and it is announced and undone by itself.
- It is not a profiler. For "which plugin is slow", use spark - TickWarden answers "where in my world is the load, what was going on when it lagged, and what do I change".
Support
Bug reports are welcome and get priority over feature requests. A report with your config, /tickwarden report output, the incident from /tickwarden incident and the relevant log lines gets fixed fastest.
评论 0
登录后参与评分
还没有评论,来抢沙发吧