My current guess is that it is particularly helped by having more cores. I currently reduce the number of cores for the paraview ppc64le builds - this was done back in 2020 to avoid memory issues, and I'm testing out relaxing that.
I'm quite impressed with how well s390x does with only 3 cores. vtk: https://koji.fedoraproject.org/koji/taskinfo?taskID=125225794 x86_64: 2:16:39 (-j48) aarch64: 3:44:25 (-j12) ppc64le: 5:17:29 (-j8) s390x: 6:47:39 (-j3) paraview: https://koji.fedoraproject.org/koji/taskinfo?taskID=125225830 (which bundles vtk) x86_64: 2:21:58 (-j48) aarch64: 3:26:30 (-j12) ppc64le: 12:02:47 (-j2) (still not finished) s390x: 7:42:33 (-j3)I know that it must be quite a challenge figuring out the right balance between the number of builders and how many cores per builder there are. But at least for these two packages, it seems like the ppc64le builds might benefit from some more cores.
I wonder if it would be possible to take a page from the HPC batch scheduling playbook and possibly be able to direct parallel capable builds to larger builders? And very serial jobs to low core ones, as I imagine your basic python package build probably takes about the same on 1 core as 48.
For comparison, here is a long build that isn't that different on the different architectures. I think most of the time is doing tests, but it shows that at some level the speed of the various builders are relatively equivalent - and so maybe vtk and paraview are very special packages and not worth optimizing for:
lammps: https://koji.fedoraproject.org/koji/taskinfo?taskID=125213968 x86_64: 6:34:08 aarch64: 6:44:23 ppc64le: 7:16:10 s390x: 6:43:51It might be interesting to go through build times and see if many longer jobs are unbalanced on the different architectures.
-- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@xxxxxxxx Boulder, CO 80301 https://www.nwra.com/
<<attachment: smime.p7s>>
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
