Jump to content
HWBOT Community Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Strunkenbold

  1. Strunkenbold

    Please add Intel Itanium CPUs

    Might be a good idea to get in contact with the boys from CPU-Z. I guess they would be quite interested to get some information from those rare systems. https://www.cpuid.com/contact.html
  2. Please do not make any requests here. All requests belong to their own thread. Please note, that I temporary retired from HWBOT duty due to the unknown future of the website itself, family and other personal reasons. (2018/09/12) I'm uncertain if I ever come back. For this reason, your requests will be handled by Antinomy. About Smartphones and other devices: Those wont be added to the database anymore. The reason for this is that the hwbot prime app is not getting maintained anymore. Also points for hwbot prime got disabled. The hwbot prime app collected over 8000 devices which would be actually needed to be added to the database but these are currently in some kind of queue because we stopped the automatic addition of devices as we noticed that things go wrong. There are a lot of different china phone sharing the same identification strings yet having complete different hardware, there are custom ROMs who change the identification strings to their favor and even apps who are able to completely fake the identification. This was causing chaos and it was about time to stop this. However it is still possible to add SoCs, so you are able to submit 3DMark and Geekbench scores. About adding peripheral Hardware : At the moment Antinomy and me just have the possibility to add CPU's, GPU's, Motherboards, Chipsets and Manufactures to the Hardware Database. Everything else needs to be done by the website owner. However these requests will take more time as Frederik is only rarely visiting this forums. So stuff like PSUs, SSDs, HDDs or Ramkits will likely not be added to db anymore. I still encourage you to open a thread for your requests. However, there hasnt been any new additions of those things in the last six months. I plan to update this page as frequent as possible. However I don't include additions of motherboards in detail. February, 9th 2019 added PCIe 4.0 added Athlon 240GE, Epyc 7371, Athlon II X4 610E, 615E added Core i9 9990XE, Core i9 9900KF, Core i7 9700KF, Core i5 9600KF, Core i5 9400(F), Core i3 9350KF fixed name W-3175X to Xeon W-3175X added Radeon VII, Radeon Instinct Mi50, 60 November, 12th 2018 added Radeon RX 590 added Radeon Pro V340 added Radeon Pro Vega 16/20 October, 30th 2018 added A8-7870 added Athlon 200GE (work by Antinomy) added Athlon PRO 200GE September, 19th 2018 added Ryzen 5 2600H, Ryzen 7 2800H added Radeon Pro WX 4150 September, 12th 2018 added Athlon 220GE, Athlon Pro 220GE fixed Core name of Phenom II X4 650T from Thuban to Zosma (reported by cbjaust, work by Antinomy) added Ryzen 7 Pro 2700X, Pro 2700, Ryzen 5 Pro 2600 Ryzen subfamilies where renamed as a little experiment for a complete overhaul of subfamilies in the db. Basically the name of the subfamily should better reflect the marketing name of the CPU. I.E. "Ryzen 7 (Summit Ridge)" turned into "Ryzen 7 1000 Series". Leave a comment if you like or not. added Quadro P3200 Max-Q September, 2nd 2018 added Xeon E5 2658A v3, 2698A v3 fixed naming of some Xeon CPUs, upper case "V" was turned into lower case "v" August, 20th 2018 added GeForce RTX 2060, 2070, 2080, 2080 ti moved GV100 from GeForce 2000 series to GeForce 1000 series added Xeon-D 2000 series lineup August, 16th 2018 added Quadro RTX lineup added GDDR6 (work by Frederik) fixed formatting issues in the GPU Hardware Browser (work by Frederik) fixed no CPU-Z preview picture appeared for validations mad with https adress (work by Frederik) fixed some chipsets pages where no longer accessible on the website (work by Frederik) it is now finally not longer possible to submit scores with multiple CPUs on single socket CPU systems, like 4x Core i7 7700k resulting in a 16 core result (work by Frederik) August, 13th 2018 added Geforce 705A added Xeon E5 2629 v3 (ES) added Radeon Pro WX 8200 added Kirin 658, 659 August, 6th 2018 fixed names of Threadripper 2970X, 2990X to 2970WX, 2990WX fixed frequency and tdp of Threadripper 2000 series CPUs added Threadripper 2920X added Geforce GTX 1050 Max Q August, 1st 2018 fixed wrong socket for Gemini Lake CPUs, BGA1090 instead of BGA1268 fixed name of Celeron N5000 to Pentium Silver N5000 (typo) fixed name of Pentium J5005 to Pentium Silver J5005 added Q270, C604, Gemini Lake chipsets added a little bit over 180 missing Gigabyte and Asus ROG boards to db July, 26th 2018 fixed wrong GCN architecture for "Topaz", should be GCN 3.0 instead of 1.0 added Radeon 530X / 535, Radeon Pro 555X, Radeon Pro 560X added Quadro P620, Quadro P3200, Quadro P5200 added Threadripper 2950X, 2970X added Core i5 8200Y, i7 8500Y added Xeon E-2000 lineup (total count: 10) added Core i9 9900K, i7 9700K added B450 chipset corrected socket of Epyc 7000 Series CPUs from TR4 to SP3 July, 16th 2018 added new subfamily for Exynos 9 added Exynos 9 9810 added Mali G72 MP18, Adreno 630 renamed Exynos 9 8895 Octa to Exynos 9 Octa 8895 renamed 3DFX to 3dfx July, 11th 2018 added Core i3 8100H added Coffee Lake Refresh Core i3 & i5 CPUs (total Count: 8 ) added Whiskey Lake Mobile CPUs (i5 8265U, i7 8565U) added Amber Lake-Y CPUs (m3 8100, m3 8114) split Core M subfamilies in Core m3, m5, m7 which fixes a bug in the Hardware browser displaying Core i3 mobile CPUs under the Core M category (for some unknown reason) added Ryzen Great Horny Owl embedded line up (total count: 4) added Epyc V3000 Series (total count: 8 ) added Threadripper 2990X July, 1st 2018 added Quadro P4200 added GeForce GT 330 (G92, DDR2) June, 18th 2018 added correct subfamily (Core i3 Mobile (Cannon Lake)) for Core i3 8121U added Intel UHD Graphics P630 added Ryzen 7 2700E, Ryzen 5 2600E, Ryzen 5 2500X, Ryzen 3 2300X May, 25th 2018 changed socket from bga1515 to bga1528 for CoffeeLake U chips added Core i3 7020U, Core i3 8121U (first Cannon Lake Chip!) renamed GeForce GTX 1060 to GeForce GTX 1060 6 GB (GP106), GeForce GTX 1060 (1152 Shaders) to GeForce GTX 1060 3 GB (GP106) / looks like they added memory size to the official marketing names added GeForce GTX 1060 5 GB, GeForce GTX 1060 3 GB (GP104), GeForce GTX 1060 6 GB (GP104), Quadro P500, Quadro P5000 (Notebook) added Snapdragon 630, 636, 640, 670, 710, 730, 845 April, 21st 2018 deleted K6 200MHz (Little Foot) and K6 233MHz (Little Foot) since these didn't exist on the market (work by Antinomy) Set GPU core to VegaM for Vega M IGPs instead of Raven Ridge. VegaM is GCN 4.0 fixed various typos in CPU names, Celeron D and Pentium M had a comma in their frequency instead of a dot April, 14th 2018 Added Core i7 8086K Added AMD X470 Deleted Embedded MMX 200 and Embedded MMX233 (work by Antinomy) Fixed Embedded 166MMX core - it's Tillamook (work by Antinomy) Renamed "Mobile Pentium MMX 166MHz" to "Mobile Pentium MMX 166MHz (P55C)" and added "Mobile Pentium MMX 166MHz (Tillamook)" (work by Antinomy) Renamed "Mobile Pentium MMX 200MHz" to "Mobile Pentium MMX 200MHz (Tillamook)" and added "Mobile Pentium MMX 200MHz (Tillamook)" (work by Antinomy) Set Tillamook 166 and 200 socket to TCP320 (work by Antinomy) Changed socket 5 Pentium Overdrive core from P5 to P54CS (work by Antinomy) Fixed typos with Mhz@MHz and Cyrix MII names (work by Antinomy) April, 4th 2018 Added Coffee Lake CPU lineup (total count: 28) Added Xeon E-2xxxM CPUs (total count: 2) Added Coffee Lake Chipsets Added Coffee Lake IGPs: UHD Graphics 630 (mobile), UHD Graphics 610, Iris Plus Graphics 655 Added Geforce GT 1030 (DDR4), Quadro GV100 March 2018 Added AMD Zen+ Pinnacle Ridge lineup (total count: 4) Cleaned Geforce GT 9800 category (separated 128 Shader variants) Added Apple A10 and A11 SoCs Fixed a bug where all Apple SoCs appeared as Allwinner Fixed a bug where multiple Geforce GPUs appeared in the wrong GPU family Added missing Bristol Rigde IGPs February 2018 Added Raven Ridge CPU lineup (total count: 4) Added Core i3 8130 Added Xeon P-8136 Celeron D CPUs have now frequency and socket in parenthesis, so it should be easier for the user to pick the correct category corrected core names for several Pentium (MMX) P5 CPUs in preparation for the old school comp split Pentium P5s CPUs in more sub families Added Geforce GTX / Quadro Max-Q variants (total count: 5) Added Geforce GT 810M GK107, GK117 Cleaned Geforce GT 620M Category, added GT 620M (GF119) January 2018 Added Gemini Lake CPU lineup (total count: 6) Added Vega M, 3, 6, 8, 11 IGPs Added Kaby Lake-G CPU lineup (total count: 4) Added new Xeon-W CPUs (total count: 3) All Intel CPUs should now have their exact CPU core, corrected E/EX/EP server variants, added S/U/H/R/G CPU Core notebook/desktop variants, older CPUs have cache sizes added to their name Added missing Geforce GT415 / GT415M Added UHD Graphics 600/605 (Gemini Lake) Cleaned Geforce GTX 950M, split in DDR3 and GDDR5, added GDDR5 variant December 2017 Added Knights Mill lineup (total count: 3) Added Opteron X CPUs (total count: 3) Added multiple missing AMD and Intel 386 CPUs (total count: 9) Added 8 core variants of Ryzen 5 1600 (total count: 2) Added multiple missing AMD APUs (Bristol Ridge, Stoney Ridge, Carrizo) (total count: 12) Added Celeron M763 Fixed a bug where the Pentium M category in the hardware browser showed the wrong CPUs Cleaned Pentium M / Celeron M categories, merged J and A suffixed CPUs and other CPUs where no difference can be detected by CPU-Z July - November 2017 added Nvidia Max-Q cards added socket 2011-1 required by some Haswell and Broadwell highend Xeon CPUs added Xeon-W Series CPUs added Xeon-D Series CPUs added Xeon Bronze, Silver, Gold, Platinum CPU lineup added Atom C3000 Series CPUs added Radeon R6 and R8 Hybrid GPUs added AMD EPYC CPU Series added Ryzen Threadripper Series added Intel Coffee Lake CPUs added serveral missing Carizzo and Bristol Ridge CPUs added AMD G series embedded CPUs added Kaby Lake refresh mobile CPUs added Skylake-X / Kaby Lake-X CPUs added Radeon Sky GPUs added FireStream series GPUs added Radeon embedded series cards added Raven Ridge GPUs added Intel UHD Graphics GPUs added Radeon Instinct series cards added integrated Stoney and Bristol Ridge GPUs cleaned Geforce GTS 450 categories fixed names of ATi Mobility cards e.g. Radeon 9800 mobile turned into Mobility Radeon 9800 fixed Rage Mobility cards fixed and cleaned Mobility Radeon X700 cards January - June 2017 merged two duplicated entries of Atom Z2520 merged two duplicated entries of Atom Z3480 merged two duplicated entries of Atom Z3560 merged two duplicated entries of Atom Z3580 merged two duplicated entries of Atom Z3590 merged two duplicated entries of Atom Z3735G merged three duplicated entries of Atom Z3735F merged two duplicated entries of Atom Z2560 added Kirin 655, Exynos 9 8895 Octa, Snapdragon 835 MSM8998, Exynos 7 Octa 7870, Exynos 7 Quad 7578 merged Radeon HD 6320m and Radeon HD 6320 into: Radeon HD 6320 merged Riva TNT2 M64 and Riva TNT2 M64 16MB into: Riva TNT2 M64 AGP merged Riva TNT2 and Riva TNT2 16MB andTNT2 Pro into: Riva TNT2/TNT2 Pro added Radeon R9 390 x2, Radeon R7 350, FirePro D300, Radeon RX 580, Radeon RX 570, Radeon RX 560, Radeon RX 550, Radeon RX 540, Radeon Pro WX 7100, Radeon R7 450, Radeon R9 M470X, Radeon HD 6450M, FirePro W4190M, Radeon Pro Duo (Polaris), Radeon R7 M460, Radeon R7 A360, Radeon Pro 580, Radeon Vega Frontier Edition added Mali-T880MP12, Mali-G71 MP20, Adreno 540 added GMA600 added 3D Rage LT Pro AGP added GeForce GTX 760 x2, Titan Xp, Riva 128 PCI, Quadro M520, GeForce 910M (GK208), GeForce 910M (GF117), GeForce GT 1030, Tesla V100, Quadro P600, Quadro P1000, Quadro P2000, Quadro P3000, Quadro P4000, Quadro M1200, Quadro M2200, Quadro FX 1800M, Tesla P40 added Xeon PHI lineup added Atom x3-C3200RK, Atom x3-C3205RK, Atom x3-C3235RK, Atom x3-C3265RK, Atom x3-C3295RK, Atom x3-C3405, Atom x5-Z8330, Atom x7-Z8750, Atom x5-E8000, Atom x5-Z8550, Xeon E5 2622 v3, Core i5 7640X, Core i7 7740X, Core i7 7800X, Core i9 7900X, Core i7 7820X, Core i9 7920X, Core i9 7940X, Core i9 7960X, Core i9 7980XE, Core i3 6157U added GX-217GI, GX-420GI, Epyc 7601, Epyc 7551, Epyc 7501, Epyc 7451, Epyc 7401, Epyc 7351, Epyc 7301, Epyc 7281, Epyc 7251, Epyc 7551P, Epyc 7401P, Epyc 7351P Core name of Opteron 144-156 Socket 939 CPUs was changed from San Diego to Venus Clockspeed of Athlon XP 1800+ Thoroughbred was corrected from 1466Mhz to 1533Mhz http://hwbot.org/hardware/videocard/twister_k/ - change socket to "integrated", change core name to "8D02" (work by Antinomy) http://hwbot.org/hardware/videocard/twister/ - change socket to "integrated", core name to "8D01" (work by Antinomy) http://hwbot.org/hardware/videocard/s3g_unichrome/ - rename to "Unichrome", the "s3g" prefix duplicates family name (work by Antinomy) http://hwbot.org/hardware/videocard/s3g_unichrome_pro/ - same here, remove s3g in the name (work by Antinomy) Change Unichrome core from CLE266 to KM400 (work by Antinomy) Change name "ProSavage8 DDR " to "ProSavageDDR" like in drivers. http://hwbot.org/hardware/videocard/prosavage8_ddr/ , change core name to "8D04" (devID), change socket to "integrated" (work by Antinomy) Change "ProSavage 8A26" to "ProSavage". http://hwbot.org/hardware/videocard/prosavage_8a26/ , change socket to "integrated", change core name to "8A26" (DevID) (work by Antinomy) Intel Atom cleanup (merged duplicates, corrected core names, corrected CPU subfamilies) corrected Specs and names for Skylake-X, Kabylake-X, Ryzen CPUs Cleaned Qualcom SoCs categories
  3. Strunkenbold

    Socket 603/604 Hall of Fame

    I think he meant that the first post of this page needs an update. @richba5tard Could you fix the first post? (and hopefully take this forum thread on someday to the main page)
  4. Strunkenbold

    please add video card

    Its already there. Even it might be a little bit hidden. https://hwbot.org/hardware/videocard/radeon_r5_m330__m430__radeon_520/
  5. Strunkenbold

    Please Add CPU to database

    Damn I could swear I catched all of those K10 CPUs. But hey, there was also the 615e missing. https://hwbot.org/hardware/processor/athlon_ii_x4_610e/ https://hwbot.org/hardware/processor/athlon_ii_x4_615e/
  6. Strunkenbold

    Which socket 370 motherboard?

    I was always looking at this list: http://holicho.lib.net/wcpuidv3/wcpuidv3.htm I saw some special made boards and they used TurboPLLs on Tusl/Cusl and ST6. https://web.archive.org/web/20020613021345/http://isweb32.infoseek.co.jp/computer/atomoc/mb_st6.htm https://web.archive.org/web/20030829142535/http://www.bekkoame.ne.jp/ha/id25302/cusl2.html https://web.archive.org/web/20021016083001/http://holicho.lib.net/ But youre correct. Using this on boards which cant run bus speeds asynchronous just dont make sense. So after looking into this today, I think the only fixed input from the pll is for the clock / system time and they used the pll ic to remove the limit of the onboard pll ic. And some have fixed frequency for usb an ps/2. I think I got this wrong for some years now. So today I really learned something. Now you and other achieved over 260 Mhz without any pll mods. So this makes me wonder why the japanese boys were so keen on those turbo plls if its actually possible without.
  7. Strunkenbold

    Which socket 370 motherboard?

    Didn't some of them did a pll mod for their boards? I guess that should completely take out the problems with the PCI/agp bus. Thanks for your suggestions. Wish I had time to overclock those systems again.
  8. Strunkenbold

    Which socket 370 motherboard?

    I used many IDE drives in the past and every of them managed to let me achieve over 200 MHz FSB. If you struggle at 155 MHz, it's most likely your CPU. Only a few CPUs manage over 200 MHz on air. Most need at least SS to achieve this. But for some it's just impossible. I appreciate all those great tips in this thread. I really never thought that those cheap IDE to SATA adapters are able to handle the high PCI clocks very well. Even though I own such things, I was always too lazy to try out.
  9. Strunkenbold

    HWBOT Rev8 going live now.

    Ah now I see this. Yes this is an old bug. Appeared already multiple times in the past. IMO it's a problem how the bot handles name strings. For some reason the bot isn't able to handle exact strings. If there is something similar, it just chooses this It's like the search engine had always a bug if you search for users. Like you search for submissions from user "blablabla". If there is also a user "Blabla". The bot just shows subs from him. But the are no results from the actual "blablabla" query.
  10. Strunkenbold

    HWBOT Rev8 going live now.

    This is correct. Raven CPUs are Zen gen1. AMDs Marketing Team decided to give them 2000er numbers. Zen+ aka Zen gen 2 will have 3000er numbers BTW.
  11. Strunkenbold

    hwbot "classic" rev8

    Well the problem of global and wr points is that they are really big. While you just can get maximum 50 hardware points, it is possible to receive over 160 points for globals and 170 points for worldrecord points. In other words an active bencher which posts some high quality scores with big points can be #1 in career ranking and in seasonal ranking at the same time and he can achieve this in some months (hypothetical). I think the career ranking should reflect the effort made over some longer time and not just some months. Currently those 30 slots for hardware / global / WR fill up too quickly with current made results because global / WR points have a so much bigger influence. Regarding comp points: I think its sad that the effort made in previous years diminishes. Seasonal ranking gives the chance to see the current level of a bencher while career shows what he did over the time. Its 10 slots for those points. If we shift up hardware point slots it should not have a too big impact anymore.
  12. Strunkenbold

    hwbot "classic" rev8

    Well the point is that I didnt see too much constructive criticism in this thread. Just complaints. If you want that Frederik does change something in your direction you have to give him something he can work with. I mean it should be clear if Frederik just receives negative feedback of his work, he probably doesnt see the point to spend time on hwbot. Which ultimately means that hwbot close his doors forever.
  13. Strunkenbold

    What is a Vega 56 Nano?

    Well I think AMD had actually the intention to release it. At least it was rumored and I really thought it gets released. However, I think AMD did not introduce another marketing name for it when the powercolor nano got released, so I guess it can be deleted from our db.
  14. Strunkenbold

    hwbot "classic" rev8

    So the culprit is just the seasonal team ranking? I think this can be easily changed back to an all time ranking again. I dont see why this needs to be seasonal. Actually first I thought the seasonal ranking just add more complexity but the more I think about it the more I like the idea. The seasonal ranking idea has the advantage to attract new benchers to easily climb up. I mean hwbot is over 10 years old, if the ranking would be static for all times, newcomers see those thousand and thousands of points and give up early. Cause it makes a difference if you had 10 years time to bench those gazillion hardware / benchmark combinations or just some months. However the current approach to calculate the career points needs to get tweaked. As currently, if you have benched a lot of current gen hardware, you are way too good in the career ranking which pisses people who are here for a long time. As we all know, there is a new hardware generation coming each year, and each year world records gets beaten by new hardware. If I take a look at the profile of splave http://uat.hwbot.org/user/splave/#Points I see that his seasonal ranking doesnt differ much from his career ranking which leaves the question why having two rankings if it acutally doesnt look much different. So my proposal is to remove global points from career ranking and increase the submissions taken into account for the ranking, maybe to 50 hardware and 30 competition. Just to make a difference between one year and 10 years contribution to the bot. The seasonal ranking is a nice idea. But you also have to see that points get zeroed every year. So it might be also a good idea to create new achievements like best overclocker 2017 or something. And introduce rankings or leader boards for the last years. So we all could see who was the best of 2010 or something.
  15. Strunkenbold

    Please add old IIT 3c87 FPU processor

    Well that is something unique for sure. However if I understand correctly, those Co processors can just work with a main CPU. Is any program able to detect those combos? I mean, I dont know if it makes sense to add co processors at all to the db, probably need another opinion from Antinomy here.
  16. Strunkenbold

    hwbot "classic" rev8

    Dead links on uat. Is anywhere else a description how those points come together (for the users)?
  17. Strunkenbold

    hwbot "classic" rev8

    Okay misunderstood the focus then. As no one replied after your RFC, I should say that it was just my personal impression that we should make the point algorithm easier. As I thought that the many broken rankings are because of this too complex algorithm. My personal motivation has been always the points I got in a ranking. I never cared too much about my ranking in a league. So thats the reason my focus seems to be different from the other guys. If rankings could get fixed and work more reliably, plus the socket ranking pages, I would be very satisfied.
  18. Strunkenbold

    hwbot "classic" rev8

    hmm and I thought changing the point algorithm to something better understandable and simpler is all about this new rev... I mean, I understand that you have to keep those percentages for lower server load but I think the biggest problem of the current rev are strange and broken rankings. Youre right, I was wrong about the percentages, mixing hardware and global, but IMO the percentages should be really reverse. 50% for the globals, means like 4Ghz scores get global points where the 75% cliff for hardware points makes Air and Water benchers unhappy...
  19. Strunkenbold

    hwbot "classic" rev8

    It would be very nice if this longstanding bug could be finally fixed. I think this is the reason for some serious problems on the website.
  20. Strunkenbold

    hwbot "classic" rev8

    This all looks very promising, great job! Some small additions: Im not a big fan of the 50% cliff for the hardware points. I often see very weird rankings because of this. And its not good to build up rankings because user on air have no motivation to post results once a LN2 score got uploaded. If we want too keep the cliff I have the following ideas (not sure how hard it would be to implement): 1. To feed the ranking with results, award the first 25 results always with points regardless of 50%. If possible visualize those 25 places with another color or something else so people get the idea. 2. Draw a red line or something in the ranking page to illustrate where the cliff begins (So people know why place 36 get points while place 37 doesnt). 3. Calculate 50% of the current first place and show the number in the ranking page so people know which score they have to beat to get points.
  21. Strunkenbold

    hwbot "classic" rev8

    +1 Would be very very cool to have this on the regular page instead hidden in the forums. I think this should be possible without too much problems, I mean I can search for SuperPi results for Socket 478 too and those get sorted by the best result. Why shouldnt it be possible to create a page for this?
  22. Strunkenbold

    Please add old cpu ng80386sx-33

    http://hwbot.org/hardware/processor/am386_sxsxl_33/ Dont know if I should go with this name scheme though.
  23. We unfortunately encountered a CPU-Z bug beginning from version 1.69 which was released on March 19th, 2014 until version 1.84 which was released March 20th, 2018. Basically the detection mechanism of CPU-Z for old Socket 5/7 Pentium's, Cyrix, Winchip, K6 CPU's was broken and produced wrong results. Antinomy digged a little bit deeper, so here is what he found out: I experienced this bug already 3 years ago and reported it to the CPU-Z bug thread here in the forums. When I checked results for the Old School is Best School competition I stumbled about the problem again, so unfortunate the bug wasn't been fixed in the last years. I contacted Frank Delattre from CPU-Z and he finally fixed the bug. One minor disadvantage is that we have now no longer FSB detection on these old chips. If you want to submit Motherboard frequency results, you have to use at least a K6-2 from now on. I went through our db and saw some results which are affected by this bug. Too keep the integrity of our db, I will remove the following submissions: http://hwbot.org/submission/2951225_chentinox_cpu_frequency_pentium_100mhz_75_mhz http://hwbot.org/submission/2965665_trodas_cpu_frequency_pentium_90mhz_75_mhz http://hwbot.org/submission/2965715_trodas_cpu_frequency_k5_pr75_75_mhz http://hwbot.org/submission/2970113_trodas_cpu_frequency_pentium_90mhz_82.5_mhz http://hwbot.org/submission/2969709_trodas_cpu_frequency_k5_pr75_82.5_mhz http://hwbot.org/submission/2963206_trodas_cpu_frequency_pentium_90mhz_90_mhz http://hwbot.org/submission/2965660_trodas_cpu_frequency_k5_pr75_90_mhz http://hwbot.org/submission/2983806_marquzz_cpu_frequency_pentium_100mhz_99_mhz http://hwbot.org/submission/3389115_stingeryar_cpu_frequency_pentium_100mhz_99_mhz http://hwbot.org/submission/2964194_trodas_cpu_frequency_pentium_90mhz_99_mhz http://hwbot.org/submission/2950923_deadthings_cpu_frequency_pentium_100mhz_100_mhz http://hwbot.org/submission/2953470_deadthings_cpu_frequency_k5_pr166_100_mhz http://hwbot.org/submission/3017463_michaelnm_cpu_frequency_k5_pr133_110_mhz http://hwbot.org/submission/2962672_trodas_cpu_frequency_pentium_90mhz_112.5_mhz http://hwbot.org/submission/2933960_johan45_cpu_frequency_pentium_mmx_166mhz_120_mhz http://hwbot.org/submission/3635152_remarc_cpu_frequency_pentium_90mhz_125_mhz http://hwbot.org/submission/2970031_trodas_cpu_frequency_pentium_90mhz_125_mhz http://hwbot.org/submission/3689830_iphone_bomgi_cpu_frequency_pentium_100mhz_132_mhz http://hwbot.org/submission/2925263_mr.paco_cpu_frequency_k6_233mhz_(model_6)_132_mhz http://hwbot.org/submission/3686726_omega_man_cpu_frequency_pentium_100mhz_132_mhz http://hwbot.org/submission/3635045_remarc_cpu_frequency_pentium_100mhz_150_mhz http://hwbot.org/submission/3688388_omega_man_cpu_frequency_pentium_133mhz_198_mhz http://hwbot.org/submission/3688332_omega_man_cpu_frequency_pentium_120mhz_198_mhz http://hwbot.org/submission/3635048_remarc_cpu_frequency_pentium_133mhz_210_mhz http://hwbot.org/submission/3016927_trodas_cpu_frequency_pentium_overdrive_mmx_200mhz_225_mhz http://hwbot.org/submission/3372942_max1024_cpu_frequency_2x_pentium_mmx_233mhz_231_mhz http://hwbot.org/submission/3764884_kotori_cpu_frequency_pentium_166mhz_250_mhz http://hwbot.org/submission/3801697_macsbeach98_cpu_frequency_pentium_mmx_166mhz_250_mhz http://hwbot.org/submission/2508087_antinomy_cpu_frequency_winchip_2_240_250.12_mhz http://hwbot.org/submission/3339373_max1024_cpu_frequency_embedded_pentium_mmx_266mhz_264_mhz http://hwbot.org/submission/3797837_jurin1388_cpu_frequency_pentium_mmx_200mhz_297_mhz http://hwbot.org/submission/3340202_max1024_cpu_frequency_embedded_pentium_mmx_266mhz_297_mhz http://hwbot.org/submission/3787426_griff_cpu_frequency_pentium_mmx_166mhz_300_mhz http://hwbot.org/submission/3802171_macsbeach98_cpu_frequency_pentium_mmx_166mhz_300_mhz http://hwbot.org/submission/3789220_macsbeach98_cpu_frequency_pentium_mmx_233mhz_300_mhz http://hwbot.org/submission/3794507_hyve_cpu_frequency_pentium_mmx_233mhz_330_mhz http://hwbot.org/submission/2931993_mr.paco_cpu_frequency_6x86mx_pr300_332_mhz http://hwbot.org/submission/3399763_michaelnm_cpu_frequency_pentium_mmx_166mhz_350_mhz http://hwbot.org/submission/3331215_max1024_cpu_frequency_pentium_mmx_233mhz_350_mhz http://hwbot.org/submission/3457688_max1024_cpu_frequency_embedded_pentium_mmx_266mhz_500_mhz I know that some of these score are perfectly valid, CPU frequency wise. But keep in mind that we are a small team and I we dont have time to discuss every single result. If a result cant be trusted, it will be removed. It took 4 years to fix this bug and another half year to clean the db.
  24. Some of you may already noticed that for some sockets the possibility to submit with more than one CPU disappeared. The background is that we had a lot of subs with incorrect core count. Some users probably got confused by the field and thought they have to enter their core count in the first field. Of course our Hardware Database already knows which core count your CPU has (except the maintainer made a mistake), so you dont have to do this. This resulted in dual cores appeared in quad core ranking or quad cores appeared in 16 core ranking. Like a Core i7 4770k entered as 4x was suddenly making a appearance in the sixteen core Global Points ranking for Cinebench R15 and of course, scored a gold cup for the hardware ranking. To solve this we implemented a function to prevent selecting multiple CPUs once you choose a CPU which only works with single socket systems. The only exceptions are sockets like LGA2011, LGA2011-3 which can host single Desktop CPUs as well as Dual Xeons. If you spot such submissions please report. Frederik ran a query to automatically move all wrong results back to their actually meant ranking, which affected almost 10k results. Unfortunately due to a bug not all subs got catched. I still see a lot of XTU results appearing in the wrong ranking. But I think its still a step in the right direction.
  25. Strunkenbold

    The Official Team CUP 2018 DDR3 stage thread:

    Just want to say that we mostly rely on data from CPU-World and TPU GPUDB. I know that CPU-Z as GPU-Z have problems showing the correct code name for recycled or castrated parts. That often happens if the vendor doesnt change the IDs of those parts. Thats the reason why CPU-Z /GPU-Z doesnt match our db in some cases. On that FM1 performance issue: I put an answer already in the _mat's thread where he examined the issue. But in case you didnt read yet... The reason why older bios versions are faster is that AMD turned of a feature of those CPUs because they found a bug which can cause the CPUs to hang. GPUPI makes heavy use of division operations. Llano CPUs actually have a unit that can do those division operations very fast. But because of a bug, AMD decided to turn that unit off. Those operations need to go through other units of the CPU now which are a lot slower. In case you ask now why nobody in the last 7 years bothered, the reason is that division operation seem to be just not that important under normal workloads, yet GPU-PI makes heavy use of it. If you want to re-enable the performance, without downgrading your Bios or your OS: https://www.passmark.com/forum/performancetest/3705-amd-llano-a-series-benchmark-and-cpu-bug?t=3656 Cbjaust already confirmed that it works.