Max method seems to be sequential for large data on CPU backend. While iterating over whole data using gfor is much faster.
I wanted to use atomic intrinsic methods with gfor but they are unsupported.

Description

• With a large data loaded it takes up to about 10 seconds
• Did you build ArrayFire yourself or did you use the official installers? official installer (v 3.7.2)
• Which backend is experiencing this issue? CPU. I've not tested other backends
• Do you have a workaround? I wanted to use atomic intrinsic methods with gfor but they are unsupported
• Can the bug be reproduced reliably on your system? Yes

Reproducible Code

• const auto maxValue = af::max(data);

System Information

ArrayFire Version: 3.7.2
Device: Intel Core i5
Operating System: Windows 10
Info:
ArrayFire v3.7.2 (CPU, 64-bit Windows, build 218dd2c)
[0] Intel: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz

Checklist

• I have read timing ArrayFire