bngblaster report.json show throughput(tx/rx-pps) as '0' when we have more pppoe subscribers (1024 in this case)

[rsys-mponnusa]

1.from config.json file
Rate - 0.1 Mbps
Length - 1460
number of subscribers -1024

throughput = config["Mbps"] * 1000000 / 8 / length_per_packet = 8.561643835616438

2.repot.json file ( find attached report file. for most of the subscribers it shows '0' ahd few subscribers it shows value as '7')
"rx-pps": 0,
"tx-pps": 0,
"rx-pps-max": 8,
"tx-pps-max": 8,

Queries:
1.When we have more subscribers (1024) on the report we see rx-pps & tx-pps are '0' for many sessions, Is there way to make this counters showing values for all subscribers?
2.can we make it exact throughput (without round-off)?

**

run_report.json
run.json
run.log
config.json

**
/usr/sbin/bngblaster
-C /var/bngblaster/TEST/config.json
-S /var/bngblaster/TEST/run.sock
-J /var/bngblaster/TEST/run_report.json
-j session
-j streams
-L /var/bngblaster/TEST/run.log
-l error
-l ip
-l info
-l pppoe
-P /var/bngblaster/TEST/run.pcap

Attachements
1.config & report file for test with 1024 subscribers

[GIC-de]

The "rx-pps" and "tx-pps" metrics reflect the real-time state. As a result, in the final report after a test has stopped:

• Sessions that ended earlier may display a value of 0.
• Sessions that stopped last might show values like 7.

This behavior is intentional and aligns with the design, which is why we introduced "rx-pps-max" and "tx-pps-max".

The "rx-pps" and "tx-pps" metrics are intended for monitoring rates while the session is still active, using CLI/API commands.