
Massman
Members-
Posts
19362 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Forums
Events
Blogs
Everything posted by Massman
-
No HWBOT friends? I think Christian Ney wants to be your friend.
-
it's this one.
-
Oh, right. What about cold scaling?
-
faust2016 - DDR3 SDRAM @ 1320MHz - 1320 MHz Memory Clock
Massman replied to LaTour's topic in Result Discussions
Oh, nice! -
Hard to beat that price/perf I guess.
-
We know what it does on a high-level. We also know the performance boost it can generate in some benchmarks (between 30 and 400%). I mean. We know it's sort of legitimate and sort of not and we know the effect it has on benchmarks is of that size that it will change A LOT if allowed across the board.
-
Heh, we actually have a thread for that! Moved some posts.
-
Sampsa looks older than 17
-
The official GIGABYTE Spring Extreme Competition thread.
Massman replied to zeneffect's topic in HWBOT Competitions
Cool! Lucky draw is fine for me. Kinda avoids having to deal with verifying what cooling method was used -
The official GIGABYTE Spring Extreme Competition thread.
Massman replied to zeneffect's topic in HWBOT Competitions
Oh, really?! That's awesome!! -
Hondacity - Radeon HD 7970 - 14183 marks 3DMark06
Massman replied to Don_Dan's topic in Result Discussions
Lucky for I.nfraR.ed February has one extra day this year -
The official GIGABYTE Spring Extreme Competition thread.
Massman replied to zeneffect's topic in HWBOT Competitions
Heh. Nothing stops you from giving the prize you might win to a lucky draw . -
The official GIGABYTE Spring Extreme Competition thread.
Massman replied to zeneffect's topic in HWBOT Competitions
That's the understatement of the year. Even in SPI-32M it seems terribly slow. -
The official GIGABYTE Spring Extreme Competition thread.
Massman replied to zeneffect's topic in HWBOT Competitions
Sjeez. Bulldozer at 7.1G gives 4.438sec; Thuban at 5.4G gives 4.516sec. -
Fixed.
-
Heh, it's sort of a grey zone. - Does MVP change the benchmark code? No. - Does MVP trick the FPS directly? No. What MVP does change is the underlying assumptions of the benchmark creator. For 3DMark11, one of the underlying assumptions is that the graphics card will render each frame completely, even if it contains data that has already been rendered before. What this technology does is basically having the IGP tell the GPU "are you fucking kidding me" when it's rendering a part of the scene multiple times and tells it to do the work only once. In a way, it's similar to any software tweak that enhances the speed of the benchmark. Remember your PCMark7 tweak to boost the image rendering (set to 640x480)? It's the same principle. Adjusting LOD is the same principle, disabling services is the same principle, disabling tesselation is the same principle, doing a copy-waza is the same principle. The principle being: running the benchmark in a different way than the developer intended. Now, I can hear you say already that "lod really does boost FPS". Well, this thing sort of does too. The issue here is that the FPS counter doesn't care how much of the frame has really been rendered. So, a situation where it would render 100% + 75% + 50% + 25% + 50% of the new frame is being accounted for as 1+1+1+1+1 = 5 frames. The real amount of data rendered, however, is closer to 3 (full) frames. In theory, the software renders exactly the same scenes, but just does it a bit smarter. In a way, this technology kinda shows high highly inefficient the GPU is currently being used. Basically, when you jump up from 60FPS to 250FPS (~ 400%), it means the GPU can render (in theory) the exact same scene using 4x less resources. But, when I say in theory, I mean that's how the Whitepaper explains the concept. As far as I know, there's no technical documentation on how the redundant frames are detected or if a user can fiddle with it so it could for instance skip 'all frames'. As I mentioned before, I see the technical discussion ("could we allow the software") as a different one from the HWBOT discussion ("how does it affect points/ranks"). Having the technology 'approved' does not necessarily mean that we allow it for HWBOT points.
-
I'm sure there are overclockers younger than that. I assume the youngest, legit overclocking should be around 17y old.
-
On a serious note, I think Fredyama might be the oldest overclocker. Although I don't really have any idea about his real age ...