Windows 11, frame drops, presenting windows in performance monitor

Hi!

specs first:
Lenovo ThinkPad P15 Gen 2i
11th Gen Intel(R) Core™ i9-11950H @ 2.60GHz
32GB RAM
NVidia RTX A2000 laptop GPU

I have slight frame drops (I believe?) almost frequently about once a second, but I think it’s not exactly frequent. I started noticing it as ‘twitching’ when transforming anything (TOP or rendered SOP) across the screen horizontally or vertically. I attach the .toe but it’s really quite simple transform across the screen.

I checked the performance monitor and the biggest consumer is something called ‘presenting windows’ (see attached image). This is on windows 11. On Mac Os I cannot see this and there doesn’t seem to be any visible problem.

When I look on to monitors-dat, I see that Touch claims to be using the onboard GPU instead of RTX (see attached image), but then again I’ve tried to set everywhere that Touch would use RTX and also NVidia’s monitor shows that touch is using it. I understood somewhere that in any case my laptop’s display finally uses onboard GPU and what RTX produces is reverted to it. Is the above ‘presenting windows’ about that? Should it usually take that long? Should monitors-dat rather show RTX as a GPU?


simpletransformdrops.toe (6.1 KB)

Thanks for noticing!
Toni.

Actually the perform-chop doesn’t show any frame drops until I add more moving objects and start zooming in and out on the workspace. Then there’s some occasional flickering and sometimes tearing (I guess that’s the right word?) on the objects.

I’m also stumped by this “Presenting Windows” line. If anybody has any info regarding what it means, I’d love to hear it.

In a project I’m currently working on, I cannot reach 60fps. The only other line that eats up any time is the “Rendering a Window” line at 2.6ms. Everything else is well below 1ms. Yet, I cannot reach 60fps because “Presenting Windows” takes 30ms… I do not understand what this number means. Why is it taking so long?

I tried removing most operators and “Presenting Windows” still eats up 12ms. This is on Windows 11.