Why can the balanced preset stop below 100%?
Its peer bitfields contain no copy of piece 15. The client can acquire the other available pieces, but selecting a missing piece cannot create a provider. Completion is the client’s piece fraction, not a measure of the entire swarm.
This model grants at most one available missing piece per round; rate values do not determine its byte-transfer duration. Dynamic peer responses are randomized. The rate ratio and upload fraction are arithmetic on modeled values, not measured efficiency.
There are 16 client flags. In the balanced fixture, piece 15 is absent from every peer. Even after the client obtains pieces 0–14, it holds only 15/16 = 93.75%, displayed as 94%. A higher authored download rate cannot supply the absent flag.
BEP 3 describes advertising available pieces and verifying their hashes before announcing completion. Actual transfers involve requests, piece data, choking and interest state. This page updates flags without file bytes, sockets or integrity checks; it cannot establish protocol conformance. BEP 3: BitTorrent Protocol Specification
The selected-peer ratio divides modeled incoming rates by allocated outgoing rates. Its percentage display is capped at 100, so it hides larger ratios. Optimistic rotation uses round(interval parameter/3) simulation rounds, while Auto Run advances once per second; the parameter is not an exact protocol timer.
Reset loads a fixture and executes its first round immediately. Pause and step to examine selections and bitfields. Export and Copy JSON include model scope and rules. A new random optimistic peer or modeled response can change the next trace, so one run cannot prove an optimal strategy.
Actual piece availability, hash verification and peer transfer behavior; not the fixture rates or timing formula.