Bug 1879824 Comment 9 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Lee Salzman [:lsalzman] from comment #8)
> In that profile, it's still hitting the DrawTargetD2D1::FillCircle path, so that hasn't really changed, and is what it is as far as performance. The only real overhead I see in the front-end is from the sheer amount of FillCircle requests being submitted in the recording, which is causing us to occasionally block on waiting for buffers here.
> 
> Any thoughts, Bob?
I don't spot anything obvious we can do other that increase the max buffers.
It's an arbitrary figure, but I'm not sure how we would optimize it.
Revision 1 by
on 
(In reply to Lee Salzman [:lsalzman] from comment #8)
> In that profile, it's still hitting the DrawTargetD2D1::FillCircle path, so that hasn't really changed, and is what it is as far as performance. The only real overhead I see in the front-end is from the sheer amount of FillCircle requests being submitted in the recording, which is causing us to occasionally block on waiting for buffers here.
> 
> Any thoughts, Bob?

I don't spot anything obvious we can do other that increase the max buffers.
It's an arbitrary figure, but I'm not sure how we would optimize it.

Back to Bug 1879824 Comment 9