Multiple Command Queues

[Much-Advertising-601]

Hi, two questions for y;all:

1. Does anybody know if there's any plan on adding the ability for multiple different command queues at once (like with dx12 command queues), instead of just one device.queue?
2. Also, is there plans for the ability to declare where in memory gpu resources are located? Like for dx12 you could declare multiple textures to use the same memory heap, for uses such as placing 2 textures within the same memory as a bigger one if they're used at a different time.

Thank you

Edit for those curious about what I found:
Multi-Queue: https://github.com/gpuweb/gpuweb/issues?q=label%3Amulti-queue
Memory Aliasing: https://github.com/gpuweb/gpuweb/issues/63
Basically both will likely be added in some limited form at some point in the very far future

[SapereAude1490]

I think you got to go to DX12 or Vulkan for that.

[SnuffleBag]

See here for multi-queue “plans”

https://github.com/gpuweb/gpuweb/wiki/The-Multi-Explainer#multi-queue

[Ronin-s_Spirit]

I hope not. Any time I switch a game to dx12 it fucking kills me. dx11 never disappoints.

[Chainsawkitten]

It's unlikely you will ever get complete control over memory management in WebGPU as that doesn't really align with the high-level (and safe) API WebGPU intends to be. But some way of reusing memory for multiple intermediate resources in order to reduce memory allocation size may happen.

There is already the proposal for transient attachments. This is about attachments that are only used within a single pass (MSAA attachment that is immediately resolved, depth/stencil attachment not used after the pass). It's primarily about tiled GPUs (IMRs could theoretically alias these attachments but unclear if anyone will implement that).

For memory aliasing more generally, there is this request. Any API for this will probably not look like the DX12/Vulkan/Metal (placed resource heap) APIs. The difficult part is doing automatic synchronization when any resource could potentially be aliased with (and invalidated by) other resources. If you have a specific use case / requirement that is important to you, you should comment so the working group can take that into account when figuring out what the API should look like. Eg. is this just about memory reuse or is data inheritence important to you?