Jump to content
HWBOT Community Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


I.nfraR.ed last won the day on November 25

I.nfraR.ed had the most liked content!

1 Follower


  • Location


  • Occupation
    Web Developer


  • realname

Recent Profile Visitors

13701 profile views

I.nfraR.ed's Achievements


Explorer (4/14)

  • Reacting Well Rare
  • Dedicated Rare
  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges



  1. It's in the human nature to explain things you don't understand with something else - aliens, god, cheaters, etc.
  2. What's next, dual-core Richland with a disabled core competing in single-core rankings? PS: Great frequency!
  3. @LeeghoofdThanks for answering and I believe it must be really annoying for you already. Following the same logic, let's say I have an FX-8350 and want to run 32M. As I normally do, I will disable unneeded cores. Does that mean I need to now submit it in the 4P catergory, as opposed to before that change where you submit in the base category regardless of disabled cores - it's up to you to tune your system to get the maximum out of it. Basically the same issue that @mickulty raised, but from the FX point of view. PS: Or do I need to be careful what is disabled - am I running in "1 core per CU" or have I disabled one of the CUs and based on that submit in a different category?
  4. Why mandate anything for the single-threaded benchmarks? You want to run Pi 32M, it's your choice if you want to run it on P core, on E core, disable E cores, run single channel...whatever it works for you, the goal is to get best score possible with your system from the current bench session. Then sub it in the base (normal) category (no P, no E, no X category). IMO only one category should exist for benches like SuperPi, pifast, etc. If you want to run it with all cores enabled and get lower clocks, it's your choice, why we should care about that? That's what I fail to understand :p I guess it is down to implementation, since they are listed as different processors and each processor has the full set of benchmarks? I'm not that active anymore, so I've probably missed a lot form the ongoing discussions, so please excuse me if you read that same thing for the n-th time :d
  5. I agree single-threaded benchmarks should go into one single category. 32M is always ran on the best core anyway. I though overclocking goes hand in hand with getting the best score/performance possible out of the the hardware in a specific benchmark/game. For single-threaded benchmarks it means you want to disable everything that affects the clocks and performance in a negative way. Leaving all 6 cores on a Thuban CPU hurts CPU-NB clocks compared to e.g. 2 cores enabled, does that mean we should add another category and assign points for both? And I still don't get these P categories. For me it's all out on multi-threaded benchmarks for highest possible score, not artificially pushing the CPUs to categories with less cores, just because they are more competitive there (at least that's how it looks from "a distance"). I know it's not just black and white, but still can't get my head around that, sorry.
  6. I have another suggestion. Leave the P categories only, there aren't many globals with full cores, so they are pointless, IMO. Most people are not really interested in benching the full cores anyway it seems. Leave the 10x (P+E) category though for 12600K(F). Super Pi is not interesting either, so maybe disable global points for it. Replace it with CPU-Z bench single thread instead and give that globals. What do you think? :p On a more serious note, have you thought about single-threaded benchmarks. Browsing Pi 32M scores (1 score), I can only see them in 8P category, but nothing in normal "I don't care about how many enabled cores are there" 12900K. Is there a way to consolidate them or are people supposed to submit the same score twice (and get globals for both)? Sorry if that specific thing have been discussed before - if so, I've missed it. PS: Btw, that 8GHz valid is also in my local forum as a news and I bet noone have seen the updated articles. Damage is done.
  7. It would have been strange if you enforce "full cores + HT" for cpuz valids when you allow disabling "E" cores for other benchmarks. I think it is logical to say we need cpuz categories for P and E cores, what do you think? After all, we should maximize the fun from a single processor and push it in every ranking we possibly can. Self-checkmate (if that's a term)
  8. I have an idea. All people involved use Cyrillic alphabet, so you can change the flag to Bulgaria. I have nothing against that Plus, nowadays, everyone can identify as "anything", it seems
  9. Awesome! We all want to know if ~300 is really the upper limit of the integrated PLL. Clockgen goes to 300 only, so maybe that's not a coincidence.
  10. Who's up to some auto overclocking and validating https://github.com/irusanov/nForce2-xtreme-tweaker-vcl/releases/tag/beta-12 This includes Auto Validation Bot and some initial code for configurable INI files. settings.ini is included in the archive, but you can only control "minimizeToTray" - 0 means false, 1 is true. There's no GUI for settings yet and nothing is implemented regarding profiles, but getting there. None of the settings of the Auto Validation are saved, you have to configure them on each launch of the tweaker. For now, there are some limitations I haven't been able to fix regarding of the detection whether cpuz has fully loaded. So, in order to try the "bot", you need to first configure settings: Path to CPU-Z -> select path to cpuz executable Wait for CPU-Z -> time in milliseconds to wait for cpu-z launch 1s = 1000ms Sleep -> time to sleep between validations. It is needed, so we give time for cpuz to save the file, recent versions are very slow in this regard, so you might need to even increase this value Step -> tweaker will try to find the next FSB which is currentFSB + step. 0 is for auto and will take longest time. Ultra -> this won't update CPU frequency and FSB in the tweaker, should be lightest mode When configured, click "Run" and don't touch anything anymore. CPU-Z window needs to have the focus, so the validation works. You can manually switch to another CPU-Z tab and validation should still work. Not sure if that would reduce the load though. To stop it, click on "Stop" and close CPU-Z window manually. PS: I think it is obvious that this feature would lead to a BSOD at some point when the limit of some component is reached - whether it is CPU, RAM or FSB. It goes until crash/BSOD or manual stop. Also not sure if that would allow a higher validation compared to doing it manually, but I think it should, since it eliminates clicking on buttons and switching between windows. Either way, it's a fun experiment .
  11. Let me stir it a bit more. Big.LITTLE doesn't mean just two complexes of equal cores anymore. Just one example (yes, first 4 cores are still A78, but one is clocked higher and has twice the L2 cache). They probably can't be overclocked by the user. Would a similar desktop CPU able to compete in the single-core global category if it is possible to disable the rest of the cores? MediaTek MT6893 Dimensity 1200 5G (6 nm) 1X Ultra Core: Arm Cortex-A78 up to 3GHz with 2X L2 cache 3X Super Cores: Arm Cortex-A78 up to 2.6GHz 4X Efficiency Cores: Arm Cortex-A55 up to 2GHz Mediatek calls it 8-core. There are also other models with 2 high performance cores + 6 efficient cores = still a octa-core CPU.
  12. It's me again, beta 11 adds ability to set AGP/PCI frequency as well. It has most of the functionality I want. It even has a better granularity for the FSB frequency than clockgen. What's left is to add ability to save and load OC profiles, complete the CPU detection/info and add some options like "minimize to tray". NForce2Xtreme-v1.1-beta11.zip
  • Create New...