首页 > 解决方案 > 我将如何使用 Java 代码从 Jmeter API 使用吞吐量整形计时器?

问题描述

我想在我的 java 代码中使用使用 JMeter API 的吞吐量整形计时器。

我的目的是以编程方式在我的代码中通过 JMeter API 使用吞吐量整形计时器。

我已经通过将名为 VariableThroughputTimer.java 的类文件添加到我的项目文件夹的源目录中来引用它。

这是我的代码片段的一部分:

   //   VariableThroughputTimer
    VariableThroughputTimer timer = new VariableThroughputTimer();
    timer.setEnabled(true);
    timer.setName("VariableThroughputTimer");
    timer.setProperty("Start RPS", 1);
    timer.setProperty("End RPS", 1000);
    timer.setProperty("Duration", 60);
    timer.setComment("Table below sets request rate shcedule ant preview graph instantly shows effect of changes.");
    timer.setProperty(TestElement.TEST_CLASS, kg.apc.jmeter.vizualizers.CorrectedResultCollector.class.getName());
    timer.setProperty(TestElement.GUI_CLASS, kg.apc.jmeter.vizualizers.TransactionsPerSecondGui.class.getName());


    // Thread Group
    ThreadGroup threadGroup = new ThreadGroup();
    threadGroup.setName("Thread Group");
    threadGroup.setNumThreads(4);
    threadGroup.setRampUp(1);
    threadGroup.setDuration(1);;
    threadGroup.setSamplerController(loopController);
    threadGroup.setSamplerController(PublishController);
    threadGroup.setProperty(TestElement.TEST_CLASS, ThreadGroup.class.getName());
    threadGroup.setProperty(TestElement.GUI_CLASS, ThreadGroupGui.class.getName());

    // Test Plan
    TestPlan testPlan = new TestPlan("IOT_Jmeter");
    testPlan.setProperty(TestElement.TEST_CLASS, TestPlan.class.getName());
    testPlan.setProperty(TestElement.GUI_CLASS, TestPlanGui.class.getName());
    testPlan.setUserDefinedVariables((Arguments) new ArgumentsPanel().createTestElement());

    // HTTP Request Sampler and Header Manager
    HashTree httpRequestTree = new HashTree();
    httpRequestTree.add(mqttConnectSampler);
    httpRequestTree.add(mqttpubSampler);
    httpRequestTree.add(csvDataSet);
    httpRequestTree.add(timer);

因此,无论何时,我都会尝试执行代码。它不执行。

以下是我的 Eclipse IDE 中的日志:

2019-02-12 16:13:28 [main] INFO  StandardJMeterEngine:453 - Starting ThreadGroup: 1 : Thread Group
2019-02-12 16:13:28 [main] INFO  StandardJMeterEngine:513 - Starting 4 threads for group Thread Group.
2019-02-12 16:13:28 [main] INFO  StandardJMeterEngine:523 - Thread will continue on error
2019-02-12 16:13:28 [main] INFO  ThreadGroup:222 - Starting thread group... number=1 threads=4 ramp-up=1 perThread=250.0 delayedStart=false
2019-02-12 16:13:28 [main] INFO  ThreadGroup:236 - Started thread group number 1
2019-02-12 16:13:28 [main] INFO  StandardJMeterEngine:464 - All thread groups have been started
2019-02-12 16:13:28 [Thread Group 1-1] INFO  JMeterThread:705 - Thread started: Thread Group 1-1
2019-02-12 16:13:28 [Thread Group 1-1] INFO  FileServer:265 - Stored: C:\Users\angshuman.basak\Downloads\apache-jmeter-5.0\csvDataNew.csv
2019-02-12 16:13:28 [Thread Group 1-1] INFO  VariableThroughputTimer:304 - No further RPS schedule, asking threads to stop...
2019-02-12 16:13:28 [Thread Group 1-1] INFO  VariableThroughputTimer:319 - Stopping gracefuly threads of Thread Group : Thread Group
2019-02-12 16:13:28 [Thread Group 1-1] INFO  JMeterThread:797 - Stopping: Thread Group 1-2
2019-02-12 16:13:28 [Thread Group 1-1] INFO  JMeterThread:797 - Stopping: Thread Group 1-3
2019-02-12 16:13:28 [Thread Group 1-1] INFO  JMeterThread:797 - Stopping: Thread Group 1-4
2019-02-12 16:13:28 [Thread Group 1-1] INFO  JMeterThread:797 - Stopping: Thread Group 1-1
2019-02-12 16:13:28 [Thread Group 1-1] WARN  VariableThroughputTimer:147 - No free threads available in current Thread Group Thread Group, made 0 samples/s for expected rps 1.0 samples/s, increase your number of threads
2019-02-12 16:13:28 [Thread Group 1-1] INFO  JMeterThread:324 - Thread finished: Thread Group 1-1
2019-02-12 16:13:29 [Thread Group 1-2] INFO  JMeterThread:705 - Thread started: Thread Group 1-2
2019-02-12 16:13:29 [Thread Group 1-2] INFO  JMeterThread:324 - Thread finished: Thread Group 1-2
2019-02-12 16:13:29 [Thread Group 1-3] INFO  JMeterThread:705 - Thread started: Thread Group 1-3
2019-02-12 16:13:29 [Thread Group 1-3] INFO  JMeterThread:324 - Thread finished: Thread Group 1-3
2019-02-12 16:13:29 [Thread Group 1-4] INFO  JMeterThread:705 - Thread started: Thread Group 1-4
2019-02-12 16:13:29 [Thread Group 1-4] INFO  JMeterThread:324 - Thread finished: Thread Group 1-4
2019-02-12 16:13:29 [main] INFO  StandardJMeterEngine:223 - Notifying test listeners of end of test
2019-02-12 16:13:29 [main] INFO  FileServer:485 - Close: C:\Users\angshuman.basak\Downloads\apache-jmeter-5.0\csvDataNew.csv
2019-02-12 16:13:29 [main] INFO  Summariser:327 - summary =      0 in 00:00:00 = ******/s Avg:     0 Min: 9223372036854775807 Max: -9223372036854775808 Err:     0 (0.00%)
summary =      0 in 00:00:00 = ******/s Avg:     0 Min: 9223372036854775807 Max: -9223372036854775808 Err:     0 (0.00%)

上面的 Summariser 表示测试没有被执行。从上面的日志中,可变吞吐量计时器获取以下内容:

2019-02-12 16:13:28 [Thread Group 1-1] INFO  VariableThroughputTimer:304 - No further RPS schedule, asking threads to stop...
2019-02-12 16:13:28 [Thread Group 1-1] INFO  VariableThroughputTimer:319 - Stopping gracefully threads of Thread Group: Thread Group
2019-02-12 16:13:28 [Thread Group 1-1] WARN  VariableThroughputTimer:147 - No free threads available in current Thread Group Thread Group, made 0 samples/s for expected rps 1.0 samples/s, increase your number of threads

我想以编程方式使用吞吐量整形计时器执行代码。如果我的实现不正确或解决执行问题,我想为 VariableThroughputTimer 提供正确的代码。

非常感谢您的帮助。

标签: jmeter

解决方案


您计划如何仅使用 4 个线程达到每秒 1000 个请求?仅当您有 4 毫秒的响应时间时才有可能,这是极不可能的。

根据日志条目,您应该

线程组线程组,为预期的 rps 1.0 样本/秒制作了 0 个样本/秒,增加你的线程数`

还要确保将底层循环控制器配置为永远迭代。

展望未来,考虑使用并发线程组,该线程组可以使用调度反馈功能与吞吐量整形计时器连接,因此如果当前数量不足以达到/维持目标吞吐量,JMeter 将能够启动额外的线程。查看使用 JMeter 的吞吐量整形计时器插件文章了解更多详细信息。


推荐阅读