User talk:Mbc07: Difference between revisions

Jump to navigation Jump to search
Line 81: Line 81:


:::: I'm not convinced of that. Outside of very rare cases, there shouldn't be more than ~10% CPU speed improvement through overclocking (usually less than that), which seems unlikely to be truly significant to observed Dolphin performance. In general folks posting their overclocked speeds are just chest-thumping. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 18:32, 30 April 2017 (CEST)
:::: I'm not convinced of that. Outside of very rare cases, there shouldn't be more than ~10% CPU speed improvement through overclocking (usually less than that), which seems unlikely to be truly significant to observed Dolphin performance. In general folks posting their overclocked speeds are just chest-thumping. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 18:32, 30 April 2017 (CEST)
::::: Dolphin relies on two hard working threads and on IPC rate unlikely other applications, so even a small overclock could drastically improve Dolphin performance although it makes little to no difference in other scenarios. For reference, the overall speed improvement on "normal" use cases from the Ivy Bridge to Haswell jump was of about 10%, but on Dolphin that improvement were over 40%! We have some benchmarks on the forums and on AnandTech, I'll try to gather some real-world tests to better show what I'm talking about. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 19:53, 1 May 2017 (CEST)


:: @[[User:Kolano|Kolano]] If the guidelines were changed so that speed would not be included anymore, then certainly I would follow that. But at this time they instruct us to include the speed of the CPU ("Indicate CPU speed with a "@ #GHz" postfix listing the stock or overclocked frequency").
:: @[[User:Kolano|Kolano]] If the guidelines were changed so that speed would not be included anymore, then certainly I would follow that. But at this time they instruct us to include the speed of the CPU ("Indicate CPU speed with a "@ #GHz" postfix listing the stock or overclocked frequency").
Line 97: Line 99:


::::: So, it being "a lot of work" to change all the test entries isn't really a factor. Then I'm still trying to get an answer to my first question - Why are you editing my entries in the first place, since the manner in which I am making the entires is consistent with the Wiki guidelines? [[User:Flang|Flang]] ([[User talk:Flang|talk]]) 15:22, 1 May 2017 (CEST)
::::: So, it being "a lot of work" to change all the test entries isn't really a factor. Then I'm still trying to get an answer to my first question - Why are you editing my entries in the first place, since the manner in which I am making the entires is consistent with the Wiki guidelines? [[User:Flang|Flang]] ([[User talk:Flang|talk]]) 15:22, 1 May 2017 (CEST)
-----
:::::: <blockquote>So, it being "a lot of work" to change all the test entries isn't really a factor.</blockquote> Yes it is. All test entries across the wiki are currently consistent in the matter they omit the .0 thing, and we won't throw that consistency away. Updating the conventions to include the .0 means ALL test entries of ALL game pages (currently 3197 pages, and counting) must suddenly include it, and that's a lot of work just for a small nitpicking of yours.
:::::: <blockquote>Why are you editing my entries in the first place, since the manner in which I am making the entires is consistent with the Wiki guidelines?</blockquote> It's simple, your test entries are being edited because '''they are not''' consistent with the current conventions, if you didn't get it yet . Also, you talk as if Kolano keeps lurking in a corner just waiting for your next edit but it just happens that Kolano reviewed your edits before someone else (like me or other active users), which would also purge your .0 thing you keep nitpicking. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 19:53, 1 May 2017 (CEST)

Navigation menu