10 Replies Latest reply on Feb 17, 2017 3:02 AM by mirh

    GCN1 compute queues: the first step is admitting you have a problem.

    darkradeon

      Here is the D3D12nBodyGravity sample that AMD forked from Microsoft to add concurrent execution of a compute queue along to the default/graphics queue.

       

      As you can see, there is no compute queue at all running the sample on the R9 280 (a GCN1 GPU, second screenshot) while with the R9 380 (a GCN3 GPU, first screen-shot) everything runs fine. You can also notice issues on the flip queue, which result in application stuttering.

       

      R9_380.png

      R9_280.png

      This issue is present from some months, with the first WDDM 2.1 driver IIRC.

       

      Please note that this is NOT related to the "quick response queue" at all. This is related to the ability to running in parallel compute and default queues (that so famous part of the multi-engine D3D12 feature known as "asynchronous compute" or "async. compute" or whatever people like to call it now).

       

      Please also note that I post this "tech" stuff here because there isn't a Direct3D developer forum at all in the entire AMD Community portal.