Asynchronous Compute : what are the benefits?
- Thread starter onQ
- Start date
Little late in sharing this bit of information but I think I've figured out where that 14+4 CU line of thinking came from finally.
When reading very thoroughly through the Xbox leaked SDK usage of Async compute warrants that the default setting that only 4CU are set aside for the processing of the job. You must alter the parameter to use additional CU at your own discretion. I'm unsure if you can use Less CU.
This leads into an interesting factoid: Xbox One can only at most dispatch 3 Async jobs simultaneously and PS4 4. If of course you cannot use less than 4 CU per job.
When reading very thoroughly through the Xbox leaked SDK usage of Async compute warrants that the default setting that only 4CU are set aside for the processing of the job. You must alter the parameter to use additional CU at your own discretion. I'm unsure if you can use Less CU.
This leads into an interesting factoid: Xbox One can only at most dispatch 3 Async jobs simultaneously and PS4 4. If of course you cannot use less than 4 CU per job.
Just came across this:
http://www.dualshockers.com/2014/09...w-childrens-developer-to-save-5-ms-per-frame/
Doesn't seem that much of an improvement, but you don't get something like this that often. It also seems an interesting game in other ways:
http://www.dualshockers.com/2014/09...lighting-technology-with-new-wip-screenshots/
http://www.dualshockers.com/2014/09...w-childrens-developer-to-save-5-ms-per-frame/
Doesn't seem that much of an improvement, but you don't get something like this that often. It also seems an interesting game in other ways:
http://www.dualshockers.com/2014/09...lighting-technology-with-new-wip-screenshots/
I'm having a hard time following what you are trying to say. How did you make the leap from the XB1 SDK to something about the PS4? How does the 8 compute pipelines with 8 queues in the PS4 GPU translate to a discrete numbers of CUs for compute?
When you submit an async compute job into the system, wrt Xbox SDK the numbers of CUs that are leveraged for a job by default is '4', unless you modify it to be a larger number. This is what is written in the SDK.
The Async Controllers are looking and waiting for availability to insert work into the CUs to do. But each job requires in (xbox case) will block off at least 4 CU for the task.
If the two GPU are similar in this manner (default CU reservation) the default CU reservation is 4 CU, which is coincidentally all the hub bub about 14+4 a long time ago.
12 CUs (xbox one) = 4×3
18 CUs (PS4) = 14 + 4 = 3×4 + 4 + 2
You better not use 4 as the default CU reservation on PS4...
forumaccount
Newcomer
There's no reason it couldn't be patched in, although patches are not really the right time to be doing that sort of thing unless there's a huge, previously unnoticed performance issue on ship.
I am guessing thats because in GCN, CUs are grouped in 4s by the fact that each group share an instruction cache and a scalar data cache.
There is still no public info that you can use compute without caling DX11/12 on Xone (i.e. without API overhead).
It is possible on PS4.
Instead of 8 Aces, there are 4 Aces in fury!!
And 2 HWS, an evolution of the architecture
The compute scheduler architecture are different. The only things we know they have 2 HWS other sort of scheduler "smarter" than ACE.
sounds a bit like the ques used in the xbox one gpu. Would make sense to have specific hardware for the different "VMs"/programs that use the GPU.
ACES don't increase performance. It's just how many async threads you can hold. Each async thread grabs 4CU as written above, so number of CU/4 is the amount of concurrent threads the GPU can operate on.
In this case, 16 threads. Each ACE is 8 threads.
Similar threads
