Metal 4: Proper usage of requestResidency() with unique per-frame textures at 120fps

Question

Created 1w

Replies 1

Boosts 0

Participants 1

Hello, I have some confusion regarding ResidencySet. Specifically, about the requestResidency() function: how often should we call it?

I have a captureOutput(_:didOutput:from:) method that is triggered at 60 or 120 fps. Inside this method, I am calling the following code every frame:

computeResidencySet.removeAllAllocations()
сomputeResidencySet.addAllocation(TextureA)
computeResidencySet.addAllocation(TextureB)
computeResidencySet.addAllocation(TextureC)
computeResidencySet.commit()
computeResidencySet.requestResidency() // Should we call it every frame?

Please keep in mind that TextureA, TextureB, and TextureC are unique for each call (new instances are provided on every frame)."

Answered by HamidYusifli in 873548022

Call this method at any time before you commit the first command buffer that relies on the allocations in the residency set. This can be any noncritical moment when your app can afford the CPU time the framework needs to prepare the applicable allocations for residency. For example, you can call this method at launch or during an app state change.

Boost

Answer 1

HamidYusifli OP

1w

Accepted Answer

Recommended

Call this method at any time before you commit the first command buffer that relies on the allocations in the residency set. This can be any noncritical moment when your app can afford the CPU time the framework needs to prepare the applicable allocations for residency. For example, you can call this method at launch or during an app state change.

0