summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichel Dänzer <mdaenzer@redhat.com>2022-07-08 12:52:03 +0200
committerMarge Bot <marge-bot@gnome.org>2022-12-17 23:45:19 +0000
commita16df485db087453a5b0f4b1d533eba4751434d4 (patch)
tree50a60a0bed7404ed336c7c46594eda59994e12ec
parentca341ef1ea0c5e8ffb1ec3bc7d6762a453f4c9ff (diff)
downloadmutter-a16df485db087453a5b0f4b1d533eba4751434d4.tar.gz
clutter: Reduce default clutter_max_render_time_constant_us to 1000
Now that dynamic max render time uses a new algorithm and takes dispatch lateness into account, this seems worth a shot. We'll see how it works out in the wild. The net result compared to before these changes is still slightly higher (by ~0.5 ms) minimum latency for me, as measured by weston-presentation-shm. It should be less vulnerable to frame drops though. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2500>
-rw-r--r--clutter/clutter/clutter-main.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/clutter/clutter/clutter-main.c b/clutter/clutter/clutter-main.c
index b6fe18d7a..fbccefc0d 100644
--- a/clutter/clutter/clutter-main.c
+++ b/clutter/clutter/clutter-main.c
@@ -93,7 +93,7 @@ guint clutter_pick_debug_flags = 0;
/* A constant added to heuristic max render time to account for variations
* in the estimates.
*/
-int clutter_max_render_time_constant_us = 2000;
+int clutter_max_render_time_constant_us = 1000;
#ifdef CLUTTER_ENABLE_DEBUG
static const GDebugKey clutter_debug_keys[] = {