Skip to content

Make "normalized sess. jitter" accurate at the beginning of the session.Β #4846

@Dan-Linden

Description

@Dan-Linden

Environment

Second Life Release 7.2.2.18475198968 (64bit)

Description

While gathering performance benchmarks for the Native Apple Silicon Client, some patterns were noticed.

Immediately after logging in the "normalized sess. jitter" is often much higher than "normalized period jitter". It can take 5 to 10 minutes for "normalized sess. jitter" to match "normalized period jitter". This decreases the value of "normalized sess. jitter" for performance testing.

There is probably a lot of jitter when the viewer rendering initializes (or before the rendering initializes?), but I don't think this is valuable data.
I propose that the "normalized sess. jitter" value should start accumulating a second or two after the world starts rendering for the first time, so that the "normalized sess. jitter" is accurate from the beginning of the session.

Reproduction steps

  1. Log in
  2. Open Statistics (ctrl+shift+1)
  3. Check how close "normalized sess. jitter" is to "normalized period jitter"

Expected: They should be very close at the beginning of the session.


This repo is using Opire - what does it mean? πŸ‘‡
πŸ’΅ Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
πŸ•΅οΈβ€β™‚οΈ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
πŸ™Œ And when they open the PR, they can comment /claim #4846 either in the PR description or in a PR's comment.

πŸͺ™ Also, everyone can tip any user commenting /tip 20 @Dan-Linden (replace 20 with the amount, and @Dan-Linden with the user to tip).

πŸ“– If you want to learn more, check out our documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageFlags issues that need to be triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions