docs(*): update performance info
Signed-off-by: Rongrong <i@rong.moe>
This commit is contained in:
Rongrong
parent
45d5c0bfed
commit
3a5a0ed1b2
|
|
@ -51,7 +51,7 @@
|
|||
- Hashtags, custom title, etc.
|
||||
- Individual proxy settings for Telegram and RSS feeds
|
||||
- OPML importing and exporting (keep custom title)
|
||||
- Optimized performance (see also the [FAQ](docs/FAQ.md#q-how-is-the-performance-of-the-bot-it-appears-to-have-a-slight-memory-leak-problem))
|
||||
- Optimized performance (see also the [FAQ](docs/FAQ.md#q-how-is-the-performance-of-the-bot))
|
||||
- User-friendly
|
||||
- HTTP Caching
|
||||
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@
|
|||
- 为 Telegram 和 RSS 源配置独立的代理设置
|
||||
- OPML 导入和导出 (保持自定义标题)
|
||||
- 自定义订阅
|
||||
- 优化的性能 (参见 [FAQ](docs/FAQ.zh.md#q-bot-的性能怎么样它看起来有轻微的内存泄漏问题))
|
||||
- 优化的性能 (参见 [FAQ](docs/FAQ.zh.md#q-bot-的性能怎么样))
|
||||
- 用户友好
|
||||
- HTTP 缓存
|
||||
|
||||
|
|
|
|||
|
|
@ -12,9 +12,13 @@
|
|||
|
||||
**A**: Send `/lang` and select language again. The bot will update your command list.
|
||||
|
||||
### **Q**: How is the performance of the bot? It appears to have a slight memory leak problem.
|
||||
### **Q**: How is the performance of the bot?
|
||||
|
||||
**A**: The bot is designed to be asynchronous, so it is lightweight and fast. Even if there are over 6000 feeds, the bot can still run on a single core VPS, with an incredibly low load average (~0.2) and approximate 350MB memory usage. The bot can still work fine in such a condition and its stability and usability will not be influenced. As for the memory leak problem, it is a [known issue](https://github.com/kurtmckee/feedparser/issues/287) of an upstream library `feedparser`, and it is not a bug of the bot.
|
||||
**A**: The bot is designed to be asynchronous, so it is lightweight and fast. Even if there are over 6000 feeds, the bot can still run on a single core VPS, with an incredibly low load average (~0.2) and approximate 350MB memory usage. The bot can still work fine in such a condition and its stability and usability will not be degraded.
|
||||
|
||||
### **Q**: It appears to have a slight memory leak problem...
|
||||
|
||||
**A**: It is not a "memory leakage" but a memory fragmentation issue of `glibc`'s `ptmalloc` and not a bug of the bot. It can only be observed on Linux or macOS. Refer to [this issue](https://github.com/kurtmckee/feedparser/issues/287) for possible workarounds. Note that the official Docker image contains some workarounds to get rid of the issue. If you deployed the official Docker image but still find some "memory leakage", please raise an issue.
|
||||
|
||||
### **Q**: Why do I still receive notifications even if I mute the subscription?
|
||||
|
||||
|
|
|
|||
|
|
@ -12,9 +12,13 @@
|
|||
|
||||
**A**: 发送 `/lang` 并再次设置你的语言。Bot 会为你更新命令列表。
|
||||
|
||||
### **Q**: Bot 的性能怎么样？它看起来有轻微的内存泄漏问题。
|
||||
### **Q**: Bot 的性能怎么样？
|
||||
|
||||
**A**: Bot 被设计为异步的，因此它轻量快速。即使订阅了超过 6000 个订阅源，bot 仍然可以在单核 VPS 上运行，并维持着令人印象深刻的 load average (约 0.2)，内存占用此时大约为 350MB。在这种情况下，bot 仍然工作得很好，且稳定性和可用性不受影响。至于内存泄漏的问题，这是上游库 `feedparser` 的一个[已知问题](https://github.com/kurtmckee/feedparser/issues/287)，并非 bot 的 bug。
|
||||
**A**: Bot 被设计为异步的，因此它轻量快速。即使订阅了超过 6000 个订阅源，bot 仍然可以在单核 VPS 上运行，并维持着令人印象深刻的 load average (约 0.2)，内存占用此时大约为 350MB。在这种情况下，bot 仍然工作得很好，且稳定性和可用性不会降低。
|
||||
|
||||
### **Q**: 看起来好像有些轻微的内存泄漏问题…
|
||||
|
||||
**A**: 这并非真正的「内存泄漏」，而是 `glibc` 的 `ptmalloc` 的内存碎片化问题。这个问题只能在 Linux 或 macOS 上观察到。请参阅[这个 issue](https://github.com/kurtmckee/feedparser/issues/287) 以获取可能的变通解决方案。注意，官方的 Docker 镜像已经包含了针对这个问题的变通解决方案。如果你部署了官方的 Docker 镜像，但仍然发现了一些「内存泄漏」，请提出 issue。
|
||||
|
||||
### **Q**: 为什么我将订阅静音后仍然收到通知？
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue