const int nstripes = getNumThreads();

This doesn't look as a reliable design.
This scheme assumes that all threads has the same speed and they are not interrupted.
It is not true for OS with preemptive execution (all widely used OS for the last 25+ years). Some cores may handle background tasks or interrupts.

Also it is not true at all for CPUs with big+little design (modern ARM, Intel CPUs with P+E cores).

nstripes should be based on subtask's "grain size" (subtask time >>> scheduling overhead) instead of number of available threads.

Some information is available here:https://oneapi-src.github.io/oneTBB/main/tbb_userguide/Controlling_Chunking_os.html

Also it is not true at all for CPUs with big+little design (modern ARM, Intel CPUs with P+E cores).

And this is why I happened fix the openmp issue on macOS. I was doing benchmarking on vision transformers on onnxruntime, mnn and opencv dnn the other day, and found that both onnxruntime and mnn can run with 4 threads on my apple m1 by default, but opencv dnn uses all threads (8) instead. It is not available to set numThreads with gcd and when I tried with openmp, things went wrong with building issues.

I think somehow we should improve the multi-threading functionality of opencv, which detects big+little design and returns the numThreads of big cores if possible. Somehowcv::Range needs to support step as well in order to work with "grain size"...

I think somehow we should improve the multi-threading functionality of opencv, which detects big+little design and returns the numThreads of big cores if possible

It doesn't look as an improvement really.

E.g., in case of ARM-based phones we a already have configurations with 2 big + 6 little cores.

Again, we should not assume or rely heterogenous or same performance of threads or equality of subtasks complexity.

I am not sure what you are exactly asking for here. Basically every other**Invoker of other layers uses the same strategy. If we want to take care of big+little core CPUs, that is going to be another pull request I think.

I think somehow we should improve the multi-threading functionality of opencv, which detects big+little design and returns the numThreads of big cores if possible

It doesn't look as an improvement really.

E.g., in case of ARM-based phones we a already have configurations with 2 big + 6 little cores.

Again, we should not assume or rely heterogenous or same performance of threads or equality of subtasks complexity.

There are many error messages during the model import:

[ RUN      ] Test_ONNX_layers.LayerNorm/0, where GetParam() = OCV/CPU[ INFO:0@132.156] global onnx_importer.cpp:831 populateNet DNN/ONNX: loading ONNX v8 model produced by 'backend-test'. Number of nodes = 1, initializers = 0, inputs = 3, outputs = 3[ INFO:0@132.156] global onnx_importer.cpp:725 parseOperatorSet DNN/ONNX: ONNX opset version = 17[ INFO:0@132.156] global onnx_importer.cpp:997 handleNode DNN/ONNX: processing node with 3 inputs and 3 outputs: [LayerNormalization]:(onnx_node_output_0!Y) from domain='ai.onnx'[ERROR:0@132.156] global onnx_importer.cpp:924 populateNet DNN/ONNX: can't find layer for output name: 'Mean'. Does model imported properly?[ERROR:0@132.156] global onnx_importer.cpp:924 populateNet DNN/ONNX: can't find layer for output name: 'InvStdDev'. Does model imported properly?

We should not have them.

The reason why they exist:

1. These ONNX models are taken from the ONNX conformance tests. I think it is better not modifying them.
2. I took a look at the opencv-onnx functionalities and did not find how to remove them completely in our onnx importer:

   // Remove additional outputs (Mean, InvStdDev)if (node_proto.output_size() >1){auto outputName = node_proto.output(0);    opencv_onnx::NodeProto node_proto_ = node_proto;    node_proto_.clear_output();    node_proto_.add_output(outputName);addLayer(layerParams, node_proto_);}

@rogday Do you happen to know how to remove optional (node & graph) output in ONNX importer?

I removed optional outputs from those ONNX models in the end. Turned out it is not straightforward to modify outputs of ONNX graph proto.

Added this extra check

Thanks for the change! I learned a lot!

So if I understand correctly, you make grainsize appropriately small enough so that we can use both big and small cores, and big cores can naturally take more jobs. What about the "magic number" 1024?Like it was taken from the "bathtub curve" fromthis link?

parallel_for() strategy should rely on subtask size and the scheduling overhead. 1024 is some empiric number here which specifies size of subtask.

Okay, thanks again. Benefit a lot from this. Another question is why multiplyingp.normSize. Another empirical operation? I tried without it and the speed is like twice slower.

By the way, I found that all other**Invokers use the same strategy assuming all threads have the same performance. I think they need to be upgraded as well.