Post

Replies

Boosts

Views

Activity

Internal error using MPSCNNConvolution
Hello! I'm a long-standing user of MPSCNN framework, it usually works fine but during the implementation of one my recent networks I started to get this errors: 2023-01-06 00:17:46.017908+0600 -[44642:879994] [GPUDebug] Invalid device load executing kernel function "cnnConvWinograd_8x8_3x3_32x32_256" encoder: "", dispatch: 0, at offset 120``` Also, strangely networks produces different results over the same inputs across multiple runs. I assume there are some race conditions inside which causes that. Is it possible to somehow enforce MPSCNN to use some other implementation of convolution? Or I'm stuck with it forever?
2
0
743
Jan ’23
Parallel Metal queue for non-real time tasks
Hi, all! I have a workload where I have a real-time renderer (which runs at up to 120FPS rate depending on the device's screen) and non-real-time kernel that should run in a loop but it can't handle the 60 (even 30) FPS requirement. So what I want to achieve is to create two MTLCommandQueues where the first will handle high-priority render tasks and maintain stable 120FPS rendering and the other one will be continuously fed with non-real-time kernel tasks. Can't find anything for this in the API. Is there anyway to achieve this?
1
0
459
Nov ’21