searching for reviewer(sotaro)
389ffe7befeeee61318659e3c76b4ae2b93bb446: Bug 1484624 - Don't create texture sources if the compositor doesn't have a GL context. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Wed, 22 Aug 2018 13:59:15 +0200 - rev 830791
Push 118854 by bmo:a.beingessner@gmail.com at Wed, 22 Aug 2018 20:13:35 +0000
Bug 1484624 - Don't create texture sources if the compositor doesn't have a GL context. r=sotaro
3db3f0761004289cef06241977003539e2abef62: Bug 1483459 - Avoid copying regions before converting them to rects throughout the gfx directory. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Tue, 21 Aug 2018 14:58:47 +0200 - rev 830790
Push 118854 by bmo:a.beingessner@gmail.com at Wed, 22 Aug 2018 20:13:35 +0000
Bug 1483459 - Avoid copying regions before converting them to rects throughout the gfx directory. r=sotaro This patch was generated using a simple sed script: sed -i 's/ToUnknownRegion().GetBounds()/GetBounds().ToUnknownRect()/g' gfx/**/*.cpp gfx/**/*.h Differential Revision: https://phabricator.services.mozilla.com/D3875
cf82ec49ee1a6a33e4a860f345b63a10c94a04b6: Bug 1483459 - Don't needlessly copy regions in ContainerLayer::GetIntermediateSurfaceRect. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Tue, 21 Aug 2018 14:41:42 +0200 - rev 830789
Push 118854 by bmo:a.beingessner@gmail.com at Wed, 22 Aug 2018 20:13:35 +0000
Bug 1483459 - Don't needlessly copy regions in ContainerLayer::GetIntermediateSurfaceRect. r=sotaro Differential Revision: https://phabricator.services.mozilla.com/D3876
202fb9c610d07d734245e8b621eda8f80e3d2250: Bug 1482109 - Hook the memory pressure observer up with WebRender. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Mon, 20 Aug 2018 15:23:54 +0200 - rev 830336
Push 118832 by bmo:ntim.bugs@gmail.com at Tue, 21 Aug 2018 13:33:17 +0000
Bug 1482109 - Hook the memory pressure observer up with WebRender. r=sotaro
d4a387207b7ae2cb4a431c62ff78a526e12c2ee2: Bug 1482795 - Fix the gfx memory pressure observer. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Tue, 14 Aug 2018 21:10:11 +0200 - rev 829174
Push 118745 by maglione.k@gmail.com at Tue, 14 Aug 2018 20:34:55 +0000
Bug 1482795 - Fix the gfx memory pressure observer. r=sotaro
4bf45d1a86655070ca2e41ad97d35fab45e18908: Bug 1482109 - Use the generic memory pressure observer in PuppetWidget. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Fri, 10 Aug 2018 17:15:18 +0200 - rev 828319
Push 118671 by bmo:mstriemer@mozilla.com at Fri, 10 Aug 2018 18:51:19 +0000
Bug 1482109 - Use the generic memory pressure observer in PuppetWidget. r=sotaro
594a80cf1466e7ee67b6258f8821d11a803468cc: Bug 1482109 - Use the generic memory pressure observer in gfxPlatfrom. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Fri, 10 Aug 2018 17:15:12 +0200 - rev 828318
Push 118671 by bmo:mstriemer@mozilla.com at Fri, 10 Aug 2018 18:51:19 +0000
Bug 1482109 - Use the generic memory pressure observer in gfxPlatfrom. r=sotaro
6c09f894ccf18ccd3b472cc2810fa9811429a224: Bug 1482109 - Use the generic memory pressure observer in ClientLayerManager. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Fri, 10 Aug 2018 17:15:08 +0200 - rev 828317
Push 118671 by bmo:mstriemer@mozilla.com at Fri, 10 Aug 2018 18:51:19 +0000
Bug 1482109 - Use the generic memory pressure observer in ClientLayerManager. r=sotaro
287b6b052c20c5a0d38f9e6a99ac6c386ac88e93: Bug 1482109 - Add a generic MemoryPressureObserver. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Fri, 10 Aug 2018 17:15:02 +0200 - rev 828316
Push 118671 by bmo:mstriemer@mozilla.com at Fri, 10 Aug 2018 18:51:19 +0000
Bug 1482109 - Add a generic MemoryPressureObserver. r=sotaro
402e309359419e325967c42a51beeb97eb0971b9: Bug 1469496 - Handle video memory purge with WebRender. r=sotaro
Nicolas Silva <nsilva@mozilla.com> - Fri, 10 Aug 2018 17:14:57 +0200 - rev 828315
Push 118671 by bmo:mstriemer@mozilla.com at Fri, 10 Aug 2018 18:51:19 +0000
Bug 1469496 - Handle video memory purge with WebRender. r=sotaro
beb04e83301f593e6ccee87f167092f1aa50f8ac: Bug 1481983 - Don't mix && and ||. r=sotaro
Jeff Gilbert <jgilbert@mozilla.com> - Thu, 09 Aug 2018 01:34:12 +0000 - rev 827912
Push 118602 by wisniewskit@gmail.com at Thu, 09 Aug 2018 14:58:37 +0000
Bug 1481983 - Don't mix && and ||. r=sotaro Differential Revision: https://phabricator.services.mozilla.com/D2982
dcea9f4775fa762440fc57968f7fb94c761d0d7c: Bug 1479939 - Ensure we tell WR to remove the compositable pipelines when clearing resources. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 02 Aug 2018 00:17:36 -0400 - rev 826174
Push 118251 by bmo:mh+mozilla@glandium.org at Fri, 03 Aug 2018 02:37:41 +0000
Bug 1479939 - Ensure we tell WR to remove the compositable pipelines when clearing resources. r=sotaro MozReview-Commit-ID: AxuvERUalhb
816e0e08ca0e987934c7b341da2ac8f68198c7da: Bug 1479939 - Ensure we tell WR to remove the compositable pipelines when clearing resources. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 02 Aug 2018 00:17:36 -0400 - rev 825860
Push 118187 by kgupta@mozilla.com at Thu, 02 Aug 2018 13:25:18 +0000
Bug 1479939 - Ensure we tell WR to remove the compositable pipelines when clearing resources. r?sotaro MozReview-Commit-ID: AxuvERUalhb
2799f012459c05f34f42ae4007f3515adb902e1e: Bug 1479075 - Ensure FlushRenderingAsync actually flushes the compositor. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 28 Jul 2018 04:47:08 -0400 - rev 823822
Push 117797 by maglione.k@gmail.com at Sun, 29 Jul 2018 00:38:49 +0000
Bug 1479075 - Ensure FlushRenderingAsync actually flushes the compositor. r=sotaro MozReview-Commit-ID: AfVIwLj2YJp
840c5872d79eb1ebfd00a3d5e6795dc43ac43b1e: Bug 1479075 - Ensure FlushRenderingAsync actually flushes the compositor. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 28 Jul 2018 04:47:08 -0400 - rev 823745
Push 117777 by kgupta@mozilla.com at Sat, 28 Jul 2018 08:49:57 +0000
Bug 1479075 - Ensure FlushRenderingAsync actually flushes the compositor. r?sotaro MozReview-Commit-ID: AfVIwLj2YJp
6cbb81dd9cc7010b74d6d4dff90498e8c2f337ff: Bug 1479075 - Ensure FlushRenderingAsync actually flushes the compositor. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 27 Jul 2018 14:51:22 -0400 - rev 823663
Push 117759 by kgupta@mozilla.com at Fri, 27 Jul 2018 20:41:38 +0000
Bug 1479075 - Ensure FlushRenderingAsync actually flushes the compositor. r?sotaro MozReview-Commit-ID: AfVIwLj2YJp
34a3eff2e57581e81e5e31991eda6edb614a25f6: Bug 1478504 - Inline function only used in a couple of places. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 27 Jul 2018 09:43:41 -0400 - rev 823632
Push 117745 by bmo:wcosta@mozilla.com at Fri, 27 Jul 2018 17:51:32 +0000
Bug 1478504 - Inline function only used in a couple of places. r=sotaro MozReview-Commit-ID: JfOgsxUHSlu
3377a2e01e60071e580f73478efa8331d0655cfe: Bug 1478504 - Use NotifyPipelineRendered instead of DidComposite for WebRender. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 27 Jul 2018 09:42:30 -0400 - rev 823631
Push 117745 by bmo:wcosta@mozilla.com at Fri, 27 Jul 2018 17:51:32 +0000
Bug 1478504 - Use NotifyPipelineRendered instead of DidComposite for WebRender. r=sotaro MozReview-Commit-ID: 4eaMTEPD9NY
d86362323d9fd2dea7b5446e90d0bbccafdba012: Bug 1478504 - Inline function only used in a couple of places. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 27 Jul 2018 09:43:41 -0400 - rev 823494
Push 117700 by kgupta@mozilla.com at Fri, 27 Jul 2018 13:44:04 +0000
Bug 1478504 - Inline function only used in a couple of places. r?sotaro MozReview-Commit-ID: JfOgsxUHSlu
fc4f331ba330321f8faea7e0be9715f05fe1c017: Bug 1478504 - Use NotifyPipelineRendered instead of DidComposite for WebRender. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Fri, 27 Jul 2018 09:42:30 -0400 - rev 823493
Push 117700 by kgupta@mozilla.com at Fri, 27 Jul 2018 13:44:04 +0000
Bug 1478504 - Use NotifyPipelineRendered instead of DidComposite for WebRender. r?sotaro MozReview-Commit-ID: 4eaMTEPD9NY
1867237e64b79ec0c75a40dbdc86ddd4268d67f4: Bug 1478504 - Inline function only used in a couple of places. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 26 Jul 2018 11:15:51 -0400 - rev 823122
Push 117581 by kgupta@mozilla.com at Thu, 26 Jul 2018 16:30:05 +0000
Bug 1478504 - Inline function only used in a couple of places. r?sotaro MozReview-Commit-ID: JfOgsxUHSlu
dc28b2bceb86728897db95beb8c948ca98608c26: Bug 1478504 - Use NotifyPipelineRendered instead of DidComposite for WebRender. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 26 Jul 2018 11:15:51 -0400 - rev 823121
Push 117581 by kgupta@mozilla.com at Thu, 26 Jul 2018 16:30:05 +0000
Bug 1478504 - Use NotifyPipelineRendered instead of DidComposite for WebRender. r?sotaro MozReview-Commit-ID: 4eaMTEPD9NY
c572bc658fec6ec6904eff12350962af3346ba8c: Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:43:14 -0500 - rev 814205
Push 115131 by bschouten@mozilla.com at Wed, 04 Jul 2018 19:07:01 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro This commit implements the CONTENT_FRAME_TIME metric for the webrender code path. It follows the same structure as the previous commit implementing it for the non-webrender code path. MozReview-Commit-ID: 6aI5uISjgge
a44c2076144a486f563ab399aac33150fc9cde40: Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro, data-review=francois
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:40:10 -0500 - rev 814204
Push 115131 by bschouten@mozilla.com at Wed, 04 Jul 2018 19:07:01 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro, data-review=francois This commit adds the CONTENT_FRAME_TIME metric which tracks the time from the beginning of a paint in the content process until it is presented in the compositor. There is existing logging for frame latency which tracks from the beginning of a refresh tick until the frame is presented. This is undesirable for this probe as javascript and layout can run in this time period. So this probe uses the existing infrastructure for logging frame latency, but uses a start time from BeginTransaction in layer manager. MozReview-Commit-ID: 5z9LS3tsZTY
346b316a0fe4d127aa059e2ca98d49a0df198d22: Bug 1470901 - Record scene build, scene swap, and render times in telemetry. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 04 Jul 2018 07:52:22 -0400 - rev 814171
Push 115123 by jdescottes@mozilla.com at Wed, 04 Jul 2018 17:42:29 +0000
Bug 1470901 - Record scene build, scene swap, and render times in telemetry. r=sotaro MozReview-Commit-ID: 1a6pqa0sSrU
93e666c132f30ee6e2899ec162c225e8b2ea96d1: Bug 1470901 - Record scene build, scene swap, and render times in telemetry. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 04 Jul 2018 07:52:22 -0400 - rev 814075
Push 115082 by kgupta@mozilla.com at Wed, 04 Jul 2018 11:52:46 +0000
Bug 1470901 - Record scene build, scene swap, and render times in telemetry. r?sotaro MozReview-Commit-ID: 1a6pqa0sSrU
90513daef576e637053b3f0c745933455ff5eb0f: Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:43:14 -0500 - rev 814000
Push 115070 by plingurar@mozilla.com at Wed, 04 Jul 2018 10:16:17 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro This commit implements the CONTENT_FRAME_TIME metric for the webrender code path. It follows the same structure as the previous commit implementing it for the non-webrender code path. MozReview-Commit-ID: 6aI5uISjgge
e438548991db2848923dddd391912141814752c7: Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:40:10 -0500 - rev 813999
Push 115070 by plingurar@mozilla.com at Wed, 04 Jul 2018 10:16:17 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro This commit adds the CONTENT_FRAME_TIME metric which tracks the time from the beginning of a paint in the content process until it is presented in the compositor. There is existing logging for frame latency which tracks from the beginning of a refresh tick until the frame is presented. This is undesirable for this probe as javascript and layout can run in this time period. So this probe uses the existing infrastructure for logging frame latency, but uses a start time from BeginTransaction in layer manager. MozReview-Commit-ID: 5z9LS3tsZTY
acbf83d0071e8932b5e96016e6e39e27a7b4da8c: Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:43:14 -0500 - rev 811725
Push 114400 by bmo:rhunt@eqrion.net at Thu, 28 Jun 2018 03:04:53 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro This commit implements the CONTENT_FRAME_TIME metric for the webrender code path. It follows the same structure as the previous commit implementing it for the non-webrender code path. MozReview-Commit-ID: 6aI5uISjgge
cecb7149f50b2abe7a827dc20f1e8b8ade199258: Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:40:10 -0500 - rev 811724
Push 114400 by bmo:rhunt@eqrion.net at Thu, 28 Jun 2018 03:04:53 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro This commit adds the CONTENT_FRAME_TIME metric which tracks the time from the beginning of a paint in the content process until it is presented in the compositor. There is existing logging for frame latency which tracks from the beginning of a refresh tick until the frame is presented. This is undesirable for this probe as javascript and layout can run in this time period. So this probe uses the existing infrastructure for logging frame latency, but uses a start time from BeginTransaction in layer manager. MozReview-Commit-ID: 5z9LS3tsZTY
385a9cb5377b94304f484423957405a745d9efb6: Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:43:14 -0500 - rev 811700
Push 114393 by bmo:rhunt@eqrion.net at Thu, 28 Jun 2018 00:42:30 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro This commit implements the CONTENT_FRAME_TIME metric for the webrender code path. It follows the same structure as the previous commit implementing it for the non-webrender code path. MozReview-Commit-ID: 6aI5uISjgge
2fd8e6fb3a806e7db6633e3f83ab750608d5012a: Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:40:10 -0500 - rev 811699
Push 114393 by bmo:rhunt@eqrion.net at Thu, 28 Jun 2018 00:42:30 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro This commit adds the CONTENT_FRAME_TIME metric which tracks the time from the beginning of a paint in the content process until it is presented in the compositor. There is existing logging for frame latency which tracks from the beginning of a refresh tick until the frame is presented. This is undesirable for this probe as javascript and layout can run in this time period. So this probe uses the existing infrastructure for logging frame latency, but uses a start time from BeginTransaction in layer manager. MozReview-Commit-ID: 5z9LS3tsZTY
5d7d584fe04f645607a4d4019481a03c565fba9a: Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:43:14 -0500 - rev 811696
Push 114391 by bmo:rhunt@eqrion.net at Thu, 28 Jun 2018 00:39:21 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro This commit implements the CONTENT_FRAME_TIME metric for the webrender code path. It follows the same structure as the previous commit implementing it for the non-webrender code path. MozReview-Commit-ID: 6aI5uISjgge
7cabf2e3525221e8802a819c531cd7290d8bac8f: Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:40:10 -0500 - rev 811695
Push 114391 by bmo:rhunt@eqrion.net at Thu, 28 Jun 2018 00:39:21 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro This commit adds the CONTENT_FRAME_TIME metric which tracks the time from the beginning of a paint in the content process until it is presented in the compositor. There is existing logging for frame latency which tracks from the beginning of a refresh tick until the frame is presented. This is undesirable for this probe as javascript and layout can run in this time period. So this probe uses the existing infrastructure for logging frame latency, but uses a start time from BeginTransaction in layer manager. MozReview-Commit-ID: 5z9LS3tsZTY
731bec997017d9ecc4bc371f3455aad80c148f24: Bug 1463911 - Add a pref to force-disable WR. r=chutten,sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 10:55:33 -0400 - rev 811047
Push 114186 by bmo:jgilbert@mozilla.com at Tue, 26 Jun 2018 22:23:18 +0000
Bug 1463911 - Add a pref to force-disable WR. r=chutten,sotaro This pref can be used by users to force-disable WebRender. It is recorded in the telemetry environment so we can get a sense of how many people are setting this pref. MozReview-Commit-ID: yZSN44NMvD
c4eb93bba0953f569241d8eb98504976eb08c378: Bug 1463911 - Record the COMPOSITE_TIME telemetry probe for the WR codepath. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 10:55:26 -0400 - rev 811046
Push 114186 by bmo:jgilbert@mozilla.com at Tue, 26 Jun 2018 22:23:18 +0000
Bug 1463911 - Record the COMPOSITE_TIME telemetry probe for the WR codepath. r=sotaro On the non-WR codepath, the COMPOSITE_TIME probe records the time spent in CompositorBridgeParent::ComposeToTarget, which does all the compositing work from vsync to when stuff shows up on the screen. The equivalent on the WR codepath is spread over multiple threads, but the start is in WebRenderBridgeParent::ComposeToTarget and the end is when we decrement the pending frame count in RenderThread. So we can instrument those sites to record the interval. MozReview-Commit-ID: 5EMUzBT1f6x
b74674d04a6f4e5d5fee169e667b157fbe4e078e: Bug 1463911 - Store the WindowInfo objects on the heap. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 10:55:19 -0400 - rev 811045
Push 114186 by bmo:jgilbert@mozilla.com at Tue, 26 Jun 2018 22:23:18 +0000
Bug 1463911 - Store the WindowInfo objects on the heap. r=sotaro I'm going to make this structure a little bigger in the next patch, so to avoid the overhead of copying it around we can just store it on the heap. I also switched to using a std::unordered_map since now the value is just a pointer. MozReview-Commit-ID: 2g1Eyu95W4Q
24f80b3a0f0ff0af0e95e43af7a2a94913fca73d: Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:43:14 -0500 - rev 810910
Push 114161 by bmo:rhunt@eqrion.net at Tue, 26 Jun 2018 19:11:15 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender codepath. r=sotaro This commit implements the CONTENT_FRAME_TIME metric for the webrender code path. It follows the same structure as the previous commit implementing it for the non-webrender code path. MozReview-Commit-ID: 6aI5uISjgge
b7c2054351019bebbc44e41a5bcdfe70cc5cd743: Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:40:10 -0500 - rev 810909
Push 114161 by bmo:rhunt@eqrion.net at Tue, 26 Jun 2018 19:11:15 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro This commit adds the CONTENT_FRAME_TIME metric which tracks the time from the beginning of a paint in the content process until it is presented in the compositor. There is existing logging for frame latency which tracks from the beginning of a refresh tick until the frame is presented. This is undesirable for this probe as javascript and layout can run in this time period. So this probe uses the existing infrastructure for logging frame latency, but uses a start time from BeginTransaction in layer manager. MozReview-Commit-ID: 5z9LS3tsZTY
453b05ed1e723543eea498be08e77d3d45c6aea9: Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender code path. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:43:14 -0500 - rev 810907
Push 114159 by bmo:rhunt@eqrion.net at Tue, 26 Jun 2018 19:08:15 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the webrender code path. r=sotaro This commit implements the CONTENT_FRAME_TIME metric for the webrender code path. It follows the same structure as the previous commit implementing it for the non-webrender code path. MozReview-Commit-ID: 6aI5uISjgge
37e4e26609a5ae81f6cd9ee2b4c3a51f19aee287: Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro draft
Ryan Hunt <rhunt@eqrion.net> - Tue, 26 Jun 2018 13:40:10 -0500 - rev 810906
Push 114159 by bmo:rhunt@eqrion.net at Tue, 26 Jun 2018 19:08:15 +0000
Bug 1470528 - Implement CONTENT_FRAME_TIME for the non-webrender codepath. r=sotaro This commit adds the CONTENT_FRAME_TIME metric which tracks the time from the beginning of a paint in the content process until it is presented in the compositor. There is existing logging for frame latency which tracks from the beginning of a refresh tick until the frame is presented. This is undesirable for this probe as javascript and layout can run in this time period. So this probe uses the existing infrastructure for logging frame latency, but uses a start time from BeginTransaction in layer manager. MozReview-Commit-ID: 5z9LS3tsZTY
00bb920d375aa7bc2835dcee74f8c3667d72deea: Bug 1470901 - Record scene build, scene swap, and render times in telemetry. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 26 Jun 2018 12:13:19 -0400 - rev 810848
Push 114133 by kgupta@mozilla.com at Tue, 26 Jun 2018 16:13:47 +0000
Bug 1470901 - Record scene build, scene swap, and render times in telemetry. r?sotaro MozReview-Commit-ID: 1a6pqa0sSrU
ee69483ca3e3fd3625bafd9818ebb104ce44bb95: Bug 1463911 - Add a pref to force-disable WR. r?sotaro,chutten draft
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 17:37:34 -0400 - rev 810443
Push 113997 by kgupta@mozilla.com at Mon, 25 Jun 2018 21:37:54 +0000
Bug 1463911 - Add a pref to force-disable WR. r?sotaro,chutten This pref can be used by users to force-disable WebRender. It is recorded in the telemetry environment so we can get a sense of how many people are setting this pref.
bfd89cad3d82d1848544107d26a14d43052a72ef: Bug 1463911 - Record the COMPOSITE_TIME telemetry probe for the WR codepath. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 17:37:34 -0400 - rev 810442
Push 113997 by kgupta@mozilla.com at Mon, 25 Jun 2018 21:37:54 +0000
Bug 1463911 - Record the COMPOSITE_TIME telemetry probe for the WR codepath. r?sotaro On the non-WR codepath, the COMPOSITE_TIME probe records the time spent in CompositorBridgeParent::ComposeToTarget, which does all the compositing work from vsync to when stuff shows up on the screen. The equivalent on the WR codepath is spread over multiple threads, but the start is in WebRenderBridgeParent::ComposeToTarget and the end is when we decrement the pending frame count in RenderThread. So we can instrument those sites to record the interval.
74392304f1a07f7e2d10e586f4606c1814514dde: Bug 1463911 - Store the WindowInfo objects on the heap. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 17:37:34 -0400 - rev 810441
Push 113997 by kgupta@mozilla.com at Mon, 25 Jun 2018 21:37:54 +0000
Bug 1463911 - Store the WindowInfo objects on the heap. r?sotaro I'm going to make this structure a little bigger in the next patch, so to avoid the overhead of copying it around we can just store it on the heap. I also switched to using a std::unordered_map since now the value is just a pointer.
9a1b9f815ee89afc2f585775a5c1d339962e66c1: Bug 1463911 - Add a pref to force-disable WR. r?sotaro,chutten draft
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 10:55:33 -0400 - rev 810221
Push 113923 by kgupta@mozilla.com at Mon, 25 Jun 2018 14:56:10 +0000
Bug 1463911 - Add a pref to force-disable WR. r?sotaro,chutten This pref can be used by users to force-disable WebRender. It is recorded in the telemetry environment so we can get a sense of how many people are setting this pref. MozReview-Commit-ID: yZSN44NMvD
b57b9d6412332685b9c1a76e9f7a391377f97810: Bug 1463911 - Record the COMPOSITE_TIME telemetry probe for the WR codepath. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 10:55:26 -0400 - rev 810220
Push 113923 by kgupta@mozilla.com at Mon, 25 Jun 2018 14:56:10 +0000
Bug 1463911 - Record the COMPOSITE_TIME telemetry probe for the WR codepath. r?sotaro On the non-WR codepath, the COMPOSITE_TIME probe records the time spent in CompositorBridgeParent::ComposeToTarget, which does all the compositing work from vsync to when stuff shows up on the screen. The equivalent on the WR codepath is spread over multiple threads, but the start is in WebRenderBridgeParent::ComposeToTarget and the end is when we decrement the pending frame count in RenderThread. So we can instrument those sites to record the interval. MozReview-Commit-ID: 5EMUzBT1f6x
1ac623de80021eea0c5cb6a124da59b735c8abf5: Bug 1463911 - Store the WindowInfo objects on the heap. r?sotaro draft
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 25 Jun 2018 10:55:19 -0400 - rev 810219
Push 113923 by kgupta@mozilla.com at Mon, 25 Jun 2018 14:56:10 +0000
Bug 1463911 - Store the WindowInfo objects on the heap. r?sotaro I'm going to make this structure a little bigger in the next patch, so to avoid the overhead of copying it around we can just store it on the heap. I also switched to using a std::unordered_map since now the value is just a pointer. MozReview-Commit-ID: 2g1Eyu95W4Q
56b432712357b3461601de27a733be3dde408def: Bug 1452375 - sse3-scaler: make sure iter->x/y is representable. r=sotaro, a=RyanVM
jmuizelaar@mozilla.com - Tue, 29 May 2018 14:27:09 +0900 - rev 806158
Push 112844 by maglione.k@gmail.com at Fri, 08 Jun 2018 22:18:59 +0000
Bug 1452375 - sse3-scaler: make sure iter->x/y is representable. r=sotaro, a=RyanVM
295b7c0fbe99c7be0c5b59beeebafb6a2fd56054: Bug 1452375 - ssse3-scaler: handle init failure. r=sotaro, a=RyanVM
jmuizelaar@mozilla.com - Tue, 29 May 2018 14:26:38 +0900 - rev 806157
Push 112844 by maglione.k@gmail.com at Fri, 08 Jun 2018 22:18:59 +0000
Bug 1452375 - ssse3-scaler: handle init failure. r=sotaro, a=RyanVM