Memory 使用长时间运行时指标了解Heroku内存

我的日志：

2015-01-11T21:27:51.320958+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.5e2ebae2-460b-481b-826a-22c41bd90695 sample#memory_total=268.89MB sample#memory_rss=268.88MB sample#memory_cache=0.01MB sample#memory_swap=0.00MB sample#memory_pgpgin=74175pages sample#memory_pgpgout=5339pages
2015-01-11T21:27:52.194907+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.471fa82a-4b2f-4819-946e-02635fe387c6 sample#memory_total=417.94MB sample#memory_rss=404.46MB sample#memory_cache=4.29MB sample#memory_swap=9.18MB sample#memory_pgpgin=747677pages sample#memory_pgpgout=643035pages
2015-01-11T21:28:07.011011+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.82a95b43-b1d8-4fb7-9329-64fefb3bfe74 sample#memory_total=310.07MB sample#memory_rss=306.77MB sample#memory_cache=3.30MB sample#memory_swap=0.00MB sample#memory_pgpgin=302671pages sample#memory_pgpgout=223294pages
2015-01-11T21:28:13.287206+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.5e2ebae2-460b-481b-826a-22c41bd90695 sample#memory_total=268.93MB sample#memory_rss=268.92MB sample#memory_cache=0.01MB sample#memory_swap=0.00MB sample#memory_pgpgin=74185pages sample#memory_pgpgout=5339pages
2015-01-11T21:28:29.199851+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.82a95b43-b1d8-4fb7-9329-64fefb3bfe74 sample#memory_total=310.26MB sample#memory_rss=306.96MB sample#memory_cache=3.30MB sample#memory_swap=0.00MB sample#memory_pgpgin=302720pages sample#memory_pgpgout=223294pages
2015-01-11T21:28:34.433135+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.471fa82a-4b2f-4819-946e-02635fe387c6 sample#memory_total=417.95MB sample#memory_rss=404.48MB sample#memory_cache=4.29MB sample#memory_swap=9.18MB sample#memory_pgpgin=747681pages sample#memory_pgpgout=643035pages
2015-01-11T21:28:35.388654+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.5e2ebae2-460b-481b-826a-22c41bd90695 sample#memory_total=268.93MB sample#memory_rss=268.92MB sample#memory_cache=0.01MB sample#memory_swap=0.00MB sample#memory_pgpgin=74186pages sample#memory_pgpgout=5339pages
2015-01-11T21:28:51.260323+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.82a95b43-b1d8-4fb7-9329-64fefb3bfe74 sample#memory_total=310.28MB sample#memory_rss=306.98MB sample#memory_cache=3.30MB sample#memory_swap=0.00MB sample#memory_pgpgin=302726pages sample#memory_pgpgout=223294pages
2015-01-11T21:28:55.235542+00:00 heroku[web.2]: source=web.2 dyno=heroku.11366593.471fa82a-4b2f-4819-946e-02635fe387c6 sample#memory_total=417.95MB sample#memory_rss=404.48MB sample#memory_cache=4.29MB sample#memory_swap=9.18MB sample#memory_pgpgin=747681pages sample#memory_pgpgout=643035pages

---

请注意，

memory\u total

在1分钟内跳跃了大量。我应该如何解释和理解这一点？

您有三种不同的dynos报告，名称为

web。2

-检查guid、

5e2ebae2-…

、

471fa82a-…

和

82a95b43-…

如果你检查每个动态对象旁边的记忆图形，它们对于每个动态对象几乎都是恒定的：也就是说，你没有记忆跳跃

---

为什么你有三个同名的迪诺是另一回事。也许你已经启用了预引导？这将在背景中以相同的名称启动新的dynos。

这方面运气好吗？我也在用这个拔头发。我今晚部署了，遇到了同样的问题。我对Meteor和heroku非常熟悉，在应用程序中没有太多变化。这是从今天开始的，可能就是这样。我启用了预引导。我也可能有多个彪马工人进程每个dyno。但我猜这些叉子会被归为它们的共同二元。