mapreduce allocates a lot on the CPU about metal.jl HOT 3 CLOSED

These might help:
https://developer.apple.com/documentation/metalperformanceshaders/mpsmatrixsum
https://developer.apple.com/documentation/metalperformanceshaders/mpsnnreducerowsum
https://developer.apple.com/documentation/metalperformanceshaders/mpsnnreducecolumnsum

from metal.jl.

Yeah, mapreduce is known to be slow, #46. We had sped it up at some point, but had to revert (JuliaGPU/GPUArrays.jl#454), and I haven't had the time to revisit.

Adding specializations that use MPS might be a good workaround for the common cases.

from metal.jl.

Regarding the performance of mapreduce: I think we're fine, see #303 (comment) for a benchmark

Regarding the allocations: I think we can close this in favor of JuliaInterop/ObjectiveC.jl#13

Basically, these aren't caused by the mapreduce implementation, but are a consequence of how the ObjectiveC object wrappers are designed (all objects being abstract types resulting in dynamic dispatch everywhere).
For example, with the simplest kernel possible:

julia> f() = @metal identity(nothing)
f (generic function with 2 methods)

julia> @time f()
  0.000177 seconds (55 allocations: 1.578 KiB)
Metal.HostKernel{typeof(identity), Tuple{Nothing}}(identity, Metal.MTL.MTLComputePipelineStateInstance (object of type AGXG15XFamilyComputePipeline))

Because of these allocations almost all coming from object instances, they are generally small and thus very fast. As such, I don't think this is a performance issue/priority right now.

from metal.jl.