Gatling - simulation.log 中的更改字段
Gatling - changed fields in simulation.log
以前的模拟日志有 4 个 long 值 (old gatling documentation):
1. first byte sent timestamp
2. last byte sent timestamp
3. first byte received timestamp
4. last byte received timestamp
计算结果：
response time (in ms) = 4 - 1
latency (in ms) = 3 - 2
目前我只看到两个值：
REQUEST Scenario 1 case 1487348824858 1487348825029 OK
这些只是第一个示例中的值 nb.1 和 nb.4？
并在此处定义 https://github.com/gatling/gatling/blob/master/gatling-core/src/main/scala/io/gatling/core/stats/writer/LeakReporterDataWriter.scala#L67?
我在这里间接找到了回复Gatling Executor for Taurus v1.9.5 (disappeared with Gatling Executor for Taurus v1.9.6)。
默认情况下它使用 Gatling 2.1.7，因为：
Taurus works with Gatling 2.2.0. However, with Gatling 2.2.0 it's not possible to extract such network stats as latency and connection time, as Gatling removed them from report data. Because of that, Taurus installs Gatling 2.1.7 by default.
通过分析这个executor, there are two data extrator, one for gatling 2.1, another for gatling 2.2的代码。
以前的模拟日志有 4 个 long 值 (old gatling documentation):
1. first byte sent timestamp 2. last byte sent timestamp 3. first byte received timestamp 4. last byte received timestamp
计算结果：
response time (in ms) = 4 - 1 latency (in ms) = 3 - 2
目前我只看到两个值：
REQUEST Scenario 1 case 1487348824858 1487348825029 OK
这些只是第一个示例中的值 nb.1 和 nb.4？
并在此处定义 https://github.com/gatling/gatling/blob/master/gatling-core/src/main/scala/io/gatling/core/stats/writer/LeakReporterDataWriter.scala#L67?
我在这里间接找到了回复Gatling Executor for Taurus v1.9.5 (disappeared with Gatling Executor for Taurus v1.9.6)。
默认情况下它使用 Gatling 2.1.7，因为：
Taurus works with Gatling 2.2.0. However, with Gatling 2.2.0 it's not possible to extract such network stats as latency and connection time, as Gatling removed them from report data. Because of that, Taurus installs Gatling 2.1.7 by default.
通过分析这个executor, there are two data extrator, one for gatling 2.1, another for gatling 2.2的代码。