unusual high credit
unusual high credit
some machines are making unusually high credit, this is an epyc vs threadripper
https://www.rechenkraft.net/yoyo/workun ... d=56426659
https://www.rechenkraft.net/yoyo/workun ... d=56426659
Re: unusual high credit
here is a different wingman with high benchmarks like its wingman.. the previous wu link had a host with base benchmarks. these two hosts with similar benchmarks are getting drastically different compute times but the same credit.
https://www.rechenkraft.net/yoyo/workun ... d=56432801
https://www.rechenkraft.net/yoyo/workun ... d=56432801
Re: unusual high credit
If the wu ran on the GPU only the very low cpu-time is shown and not the runtime.
On my 4300U i run M Queens on the iGPU with runtime 45 - 70min and CPU-time 45 -75 sec.
https://www.rechenkraft.net/yoyo/result ... tid=497554
On my 4300U i run M Queens on the iGPU with runtime 45 - 70min and CPU-time 45 -75 sec.
https://www.rechenkraft.net/yoyo/result ... tid=497554

Re: unusual high credit
i didnt know there were gpu apps and yoyo doesnt have a gpu column on the hosta/top computer lists.
is there an appconfig/info I can run to do only gpu tasks?
is there an appconfig/info I can run to do only gpu tasks?
Re: unusual high credit
There was a news in Dez. 2020.
The app is only for Windows and works with some AMD-GPUs.
https://github.com/sudden6/m-queens/rel ... s-ocl-v0.2
The app is only for Windows and works with some AMD-GPUs.
https://github.com/sudden6/m-queens/rel ... s-ocl-v0.2

Re: unusual high credit
I think it's EPYC CPU versus Vega VII GPU...
As the project now includes GPU apps it would be helpful if GPU type/number is stated for each host.
Or, if that spoils the site layout, the GPU model could be recorded in the stderr out perhaps?
As the project now includes GPU apps it would be helpful if GPU type/number is stated for each host.
Or, if that spoils the site layout, the GPU model could be recorded in the stderr out perhaps?
