I implied it could be a slight issue with the software only ,graphical corruption is not common imho while benching CPUs. There are too many choices to use, to be holding Ibt precious, it Agent is god eh, fine but he wrote it before Ryzen existed, and I get your point but i have experience of plenty of old software that doesn't work right after some time or has issues with a particular system/platform.
#Intel burn test for amd code
Now I am not a conspirational sort and I am not claiming to know anything for sure.īut if i got a brand new cpu of any type or brand ,then ran code on it to test just it ,if i got gpu artefacts i would find something else to test with personally ,regardless of what some might say. I said that because the OP was using this software to test his CPU ,and was getting graphical artefacts? Wtaf. I am of the opinion though ,that this old program adapted by(for) intel, on an intel compiler with a new Gui could contain glitchy code(ie the gui has code running on the same processor that's benching to display stuff ,with a guess i would say Java, it might not be the test causing issues directly, but issues do not imply reliability of the test or its minor or major fails more importantly, in this use case imho, im not a well experienced coder, more occasional but thinking logically about stuff this seam's a reasonable hypothesis) still. They would much rather skip AVX which is a high difficulty/low gains task and ensure their game runs on a toaster.Ĭlick to expand.To you and others, i realise more than you realise i do. Metro used to crash on CPUs that didn't have SSE 4.1, you can bet developers would like to avoid cases like these at all cost. And of course there is also the fact that you simply can't always make extensive use of it, in fact more often than not that's the case. Despite the name of the application, IntelBurnTest can be used on both Intel and AMD processors. Hell ,there is still a fair amount of software out there which doesn't even use the previous SSE extension, these are instructions present in all CPUs for something like a decade, SSE2 is pretty mainstream and that's close to being two decades old. The CPU test of the OCCT stress testing software also makes use of LINPACK. The ways in which you include AVX support in your software are cumbersome and involve using certain functionalities which are compiler specific which are generally avoided. if intel doesnt give you the heebee geebees, then you should get more bang for your dollar. You are simply not going to find much of it outside synthetic test. intel is usually faster, amd has always been better quality (ie less problems/errors with poor power supplies, can run high density ram, etc) amd used to offer military grade chips back in the day. I am really curios as to how you figured that must be the case or is it just an assumption as I suspect ? Though I am unaware of any statistics with regards to this, I have many reasons to believe AVX is sparingly used at best in commercial software.
0 kommentar(er)
