使用 mr.ripley 进行基准测试的语法
我有一个 Plone 3.3.5 站点，我正在将其迁移到 plone.app.blob 以进行 BLOB 存储。我希望通过在迁移前和迁移后重播对站点的请求来衡量性能和资源使用情况的差异。
我发现 mr.ripley 带有它自己的构建，我用它来安装它。该构建包含一个在 bin/replay 处创建脚本的部分，该脚本由 buildout.cfg 中的一些参数配置。包含的参数看起来应该适用于我的实例，因为我也在端口 8080 上运行。
我将我的（较小的）apache 日志之一复制到 mr.ripley 构建的基本目录中，并将其更改为 chown，以便我的 zope 用户可以读取它。然后我尝试像这样运行它：
time bin/replay mysite.com_access.log
它似乎运行了（不会产生任何错误或让我返回 shell），但是我没有看到任何迹象表明它正在加载服务器。 top 中的 RAM 和 CPU 使用情况看起来仍然像是机器处于空闲状态。
许多小时后，该过程似乎仍未完成。我使用 screen 运行它，分离并返回会话几次，但它似乎被卡住了。
关于我可能缺少什么有什么建议吗？
I have a Plone 3.3.5 site that I'm migrating to plone.app.blob for BLOB storage. I'm looking to measure the difference in performance and resource usage by replaying requests to the site, pre-migration and post-migration.
I found that mr.ripley comes with it's own buildout and I used that to install it. That buildout contains a section which creates a script at bin/replay, which is configured by some parameters in the buildout.cfg. The included parameters look like they should work for my instance as I'm running on port 8080 as well.
I copied one of my (smaller) apache logs into the base directory of my mr.ripley buildout and chowned it so that my zope user can read it. Then I try to run it like this:
time bin/replay mysite.com_access.log
It seems to run (doesn't produce any errors or drop me back into the shell) however I don't see any signs that it's loading up the server. My RAM and CPU usage in top still look like the machine is idling.
Many hours later the process does still not seem to have been completed. I ran it using screen, detached and returned several times to the session, but it just seems to be stuck.
Any recommendations as to what I might be missing?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我在负载测试之前和之后执行了负载测试来测试架构更改。为此，我们使用了 JMeter。我们获取了代表我们所追求的典型用途的 apache 日志。 JMeter 允许重播这些内容。此外，它还会模拟 cookie/会话和浏览器缓存响应，使请求更加真实。
然后我们构建了一个构建来部署 jmeter 并将其配置到多个测试节点并让它运行。
我知道这并不能回答你的直接问题，但这是一种替代方法。
I've performed before and after load testing to test architecture changes. To do this we used JMeter. We took apache logs that represented the typical use we were after. JMeter allows these to be replayed. In addition it will simulate cookies/sessions and browser cache responses to make the request even more realistic.
Then we built a buildout to deploy jmeter and it's configuration out to several test nodes and let it run.
I know this doesn't answer your direct question but it's an alternative approach.