Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
mutter
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 742
    • Issues 742
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 98
    • Merge Requests 98
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • mutter
  • Merge Requests
  • !651

Closed
Opened Jun 26, 2019 by Daniel van Vugt@vanvugtContributor
  • Report abuse
Report abuse

WIP: clutter/stage-cogl: Factor in pending_swaps to next_presentation_time [performance]

  • Overview 19
  • Commits 1
  • Pipelines 15
  • Changes 1

get_update_time was returning -1 in some cases even if schedule_update was called prior. So the master clock was overshooting the correct update time and missing some frames. This seems to be happening most under moderate CPU load (gnome-shell#1411 (closed)), but not so high a load as to justify the frame skips that were occurring.

The reason for get_update_time returning -1 in these cases was because it was considered impossible to calculate the next update time while pending_swaps > 0. That's not completely true. We know if pending_swaps == 1 then schedule_update should schedule one frame later. So just factor pending_swaps into schedule_update. Now get_update_time won't return -1 in these cases so we're more likely to render the next frame (or move the cursor) at the correct time.

Closes: gnome-shell#1411 (closed)

Prerequisite (just FYI for backporters): !216 (merged)

Edited Aug 06, 2019 by Daniel van Vugt
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: GNOME/mutter!651
Source branch: schedule-later