Transform Feedback performance on PowerVR

This topic contains 3 replies, has 2 voices, and was last updated by  Dark_Photon 2 years ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #51446

    How do you maximize Transform Feedback performance on PowerVR 6 GPUs?

    EXAMPLE: Consider iteratively running transform feedback to generate transformed vertices and then render the result, repeating this multiple times per frame. Suppose you write-to/read-from the “same” region in the same buffer for each iteration. Is this a problem?

    If so, how about using “different” regions in the same buffer for each iteration? What about different buffers? What about using different regions of the same buffer “if” the TF passes are grouped together before any of the draws sourcing from the buffer?

    MOTIVATION: The reason I ask this question is that when we’ve tried TF before on PowerVR, the results were underwhelming. It was actually faster to transform the data on the CPU and then stream the now-larger vertex stream to the GPU for rendering. That doesn’t seem right. Feels like some driver blocks may be kicking in.

    Underlying my question is: how do we avoid all implicit pipeline blocking/synchronization in the driver associated with TF and achieve completely asynchronous submission and rendering?

    Thanks in advance for any tips!

    #51455

    pauls
    Member

    Hello Dark Photon,

    Could you please provide a trace? Otherwise, a PVRTune would help to identify if there are stalls.

    I can try to offer advice without but it would really help speed-up investigation.

    Thanks,
    Paul

    #51459

    Hi Paul. As I find time I’ll try to get that old code working so I can get you a trace. Thanks.

    #51530

    Hi Paul. Just got this shelved code largely working again and posted a trace under Ticket #612. Just search down to BeginTransformFeedback.

    Sifting the trace, I immediately see one likely problem: The template he used was:

    * Create buffers
    * Do transform feedback [write to buffer]
    * Draw call [read from buffer]
    * Delete buffers

    That last will cause a full TA flush, right?

    However, the question is: what’s the highest-performing buffer management approach to be using here with Transform Feedback on PowerVR GPUs (I threw out a few options in my first post to consider).

    Thanks!

Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic.