mojira.dev
MC-240559

JFR JSON report's bytesPerSecond is incorrectly calculated

JFR JSON report's bytesPerSecond in network section is incorrectly calculated and always equals countPerSecond when it should not.

JFR JSON report includes bytesPerSecond key and countPerSecond key to indicate how many packets/how much bytes were sent/received. However, when calculating bytes per second, it reads totalCount record value instead of totalSize.

Attachments

Comments 2

Can confirm in 1.18 Pre-release 3. Using Mojang mappings, the code can be found in net.minecraft.util.profiling.jfr.stats.NetworkPacketSummary.

apple502j

billysjoberg

Community Consensus

Normal

Debug, Performance

21w44a, 1.18 Pre-release 2, 1.18 Pre-release 3, 1.18 Pre-release 4, 1.18 Release Candidate 1, 1.18 Release Candidate 2, 1.18, 1.18.1 Release Candidate 2

22w03a

Retrieved