对网络应用程序进行负载和压力测试

发布于 2024-08-31 16:19:30 字数 502 浏览 9 评论 0原文

客户端有一个硬件——它做什么并不重要。其中 150 台 PC 可以连接,单个服务器最多可以连接 150 台 PC。这些是他的数据,我不确定是否要查询它们。

在他的场所,他有一个宽敞的房间,墙上安装了 150 个硬件设备 - 测试包括许多人试图同时按下按钮。

他已经看到了曙光,想要进行软件模拟。那么,如何最好地进行呢?

我想,自动化的、基于脚本的测试。他的人用 C 编写代码,所以我可能用 C++ 进行测试并使用 CPPunit。

一台测试 PC 可以模拟 150x150 硬件欺骗吗?假设这取决于他们发送的流量。

我应该对其进行参数化,以驱动要模拟的单元数、它们应该执行哪些操作等?

我应该在顶部添加一个 GUI 来给管理层留下深刻印象吗?我可以用滑块控制模拟单元的数量,在直方图上显示系统负载 - 你低,图片......管理......

对这类事情有什么建议吗?有什么问题吗?好的网址、书籍吗?

我知道这可能听起来很模糊,但我确信对于此类事情有一些通用准则。

A client has a piece of hardware - it doesn't really matter what it does. 150 of them can connect to a PC and up to 150 PCs can interface to the single server. These are his figures and I and not sure if I want to query them.

At his premises he has a largish room with 150 h/w devices mounted on the walls - and testing consists of a lot of guys trying to push buttons all at once.

He has seen the light and wants to have a software simulation. So, how best to proceed?

Automated, script-based testing, I would imagine. His guys code in C, so I might do the tests in C++ and use CPPunit.

Can a single test PC simulate 150x150 hardware deceives? S'pose it depends on how much traffic they are sending.

Should I parameterize it, to drive how many units to simulate, what operations they should perform, etc?

Should I slap a GUI on the top to impress management? I could control the number of simulated units with a slider, display system load on a histogram - you low, pictures ... management ...

Any suggestions for this sort of thing? Gotchas? Good URLs, books?

I know it might sound vague, but I am sure that there are some general guidelines for this sort of thing.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

迷你仙 2024-09-07 16:19:31

非常清楚您正在测试什么。听起来目前他们测试了 150 台设备、1 台(或几台)PC 和一台服务器。这距离 150x150 台设备、150 台 PC 和 1 台服务器还有很长的路要走。

那么我们的目标是强调服务器、PC 吗?确定压力下的行为?锻炼特定的路径?

听起来您打算构建一些在 PC (LoadProducer) 上运行的软件,该软件将模拟设备,并针对真实的 PC 触发 LoadProducer。希望模仿人们按下按钮。

我认为这可能具有很大的价值。

至于附加功能,我的建议是首先获得一个简单的命令/文件驱动版本,然后考虑您是否有能力构建 UI。用户界面是一种精力消耗,如果你不先把功能做好,你的注意力就会转移到美观上。

我不会太关心你可以模拟的设备数量,肯定很多,如果不是 150 个,那么想必你只使用了几个 LoadProducer。

如果我真的想要练习PC代码,那么我可能还想模拟服务器,或者创建服务器代码的测试版本,它可以做一些有趣的事情,例如运行速度非常慢,或者发送虚假答案。

Be very clear what you are testing. Sounds like currently they test 150 devices, 1 (or a few) PCs and one server. That's a long way from 150x150devices, 150 PCs and 1 server.

So is the goal to stress the server, the PC? To determine behaviour under stress? To exercise particular paths?

Sounds like you intend to build some software to run on PC (LoadProducer) that shall emulate the devices, and fire the LoadProducer against the real PC. Hopeing to emulate people pressing buttons.

I think that this potentially has a lot of value.

As to bells and whistles, my advice is first to get a simple command/file driven version going and then consider whether you can afford to build the UI. UIs are effort sinks, if you don't get the function right first you'll allow your attentions to be diverted towards prettyness.

I would not be too concerned about the number of devices you can emulate, surely it's many, if it's not 150, then presumably you just use several LoadProducers.

If I really wanted to exercise the PC code then I might also want to emulate the server, or create a test version of the server code that can do amusing things such as go really slow, or send spurious answers.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文