yoelshoshan

If anyone is interested, i solved the problem of measuring latency.

I had to move outside of the scope of user-mode DirectX.

The solution was injecting "D3DKMT_SIGNALSYNCHRONIZATIONOBJECT2":after presents.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff548357%28v=vs.85%29.aspx

It sounds off topic for this forum so i won't go deep into the description.

Thanks for your replies =)

Hodgman, as you said - it changes performance and behavior drastically, so it's not acceptable.

The point is to measure current latency, and by doing what you suggest, not only performance is altered, latency itself is altered drastically since i no longer allow queuing of frames.

Sharing the options i can think of:

1. Using GPU time_stamp queries and somehow learning how to match between cpu time_stamp and gpu time_stamp (tricky...)

2. Polling event queries on a dedicated thread in around 1000 getdata queries per minute.
I must check how much it eats from the core it runs on... hopefully not too much since it's not a full busy polling.
3. Probably the best method remains waiting on low level events, the same way as GPUView does.

BTW - this code will not run on my own application, it is injected to other applications. But any solution that works on my own application, without altering the original latency/performance is acceptable as well

Thank you MJP!

I need to do it programatically, it's not some "post-mortem" analysis of an application.

But i can take the following from your idea:

1. What i want to do is obviously possible - If GPUView can do it, so should I =)

2. Maybe i can reverse GPUView a bit, but my guess is that they use kernel code which I don't want to do until I make sure it's not solvable in user code.

Any more ideas?