Jump to content
HWBOT Community Forums

Leaderboard

Popular Content

Showing content with the highest reputation on 12/31/20 in all areas

  1. Congrats to the winning team of Australia !!! Congrats to them , cause they are committed to having fun !!! Congrats to them , cause they are a true TEAM !!! Congrats to them , cause they show what team spirit and national pride , really means !!! A well deserved 4th in a row !!! 🏆
    4 points
  2. Nope, I added your score back to the ranking a few hours ago
    2 points
  3. Good Competition! It was close Australia, nice play holding off subs till the last few hours.:)
    1 point
  4. Seems we got some creative people inside our humble community. Someone is very frustrated with memory scores lately
    1 point
  5. Awesome work on the ic controller for the evc2 , luckily my non-reference Asrock pcb 6900xt uses the same controller. AIso thank you for sharing your findings that 100Mhz less in over driver helps. I was talking with Elmor on discord and he will write a special profile so we can take advantages of everything this cards has to offer voltage wise on evc2. Thank you for sharing 👍 as just a very few of us ( 4 or 5 ) users here at hwbot are using this cards and is very challenging going at it blind as this is all new + the amd drivers are not cooperating with mpt most of the time , but when it works it does so flawlessly. I still have to try a few things and will keep you updated on fb or team ocn discord chat. Sharing the knowledge for everyone feels awesome ! great to be part of this community here at hwbot.
    1 point
  6. Nice info. I have been setting minimum to 100mhz less than maximum on freq in over drive. More here https://www.elmorlabs.com/index.php/forum/topic/6900xt-power-limit-tricks/#postid-335
    1 point
  7. No strange problems yet. On water I get like ocp or something maybe some protection sometimes it hard shut downs the rig. Will see what adding some vgpu offset can do. First time I tried -70 was the limit for temp.
    1 point
  8. Just to clarify: I didn't add wPrime to BenchMate at first because it is not a good benchmark. Visual Basic 6 is not the right tool and therefor it was a lot of effort to support it. But I did it anyway because benchers define what is worthwhile (as in fun) and what's not. And I'm more than okay with that as long as BenchMate's security and reliability standard can be upheld. That is not the case for the x265 benchmark btw (or any other bench using Java or other interpreter languages). The above was kind of true for wPrime as I stated in my Facebook post, because the DLL changed a lot of functionality in the benchmark's workload and made the results less comparable for rankings. I personally don't consider using different DLLs a cheat. It happens all the time even without anyone's knowledge. Just using another OS version or even installing another piece of software might have an impact on a benchmark's performance. IF the benchmark's workload relies heavily on that 3rd party code (which can also be a driver or the OS in general). That's true for most benchmarks out there, especially for 3DMark and other 3D benchmarks (DirectX, display driver), PCMark, GPUPI (OpenCL, CUDA) and so on. But there are other benchmarks that are not influenced by other software. For example SuperPi, pifast and some code paths of y-cruncher I guess. In the case of wPrime we are talking about a non-bundled system DLL, that has significant changes between different OS versions. It can not be dismissed as a cheat in general, because this is just the way software works. But I do consider it a tweak of course and the bot can or can not allow it for the sanctity of their database and the process of score moderation. Bottom line is the bot could have either allowed it or removed boints. Alternatives are the bench itself gets updated (not possible for unmaintained legacy benches) or a wrapper becomes mandatory (BenchMate). In my opinion it was the right choice. wPrime does not scale above 64 cores and even worse than the DLL: it doesn't have real threading. It spawns processes through COM, which puts even more dependencies on the OS and is therefor even more uncontrollable. Good riddance.
    1 point
  9. Only BenchMate 0.9.3 supports Geekbench 3, 4 and 5. BenchMate 0.10.5 is the latest stable release, but too old for Ampere. Ampere and Vermeer are properly supported with the latest version, BenchMate 0.10.6, currently in beta. It also reintroduces Geekbench 3 with an additional legal disclaimer. It will be released very soon, but if you want to grab it today, it's available for all supporters: https://www.patreon.com/benchmate
    1 point
×
×
  • Create New...