-
The problem scales for me, though. 1M is just my way to judge if things are the same, or if they've gone back to normal. Granted, I'm in Windows 10, but on the same system with nothing changing except BIOS and Speeds (no patching, driver updates, etc), I don't see why performance has tanked in SuperPi.
Do you have a rough idea of what times, in Win10, a 32M run should pull off with CPU @ 3.8GHz and RAM @ 3333 14-14-14-35 1T (with the aformentioned SubTimings and the SCL trick)?
EDIT: Just thought of this... Wonder if the reason SPi tanking so badly is in any way related to why Task Manager is unable to figure out my CPU speed after I use K17TK to adjust P0? (literally my steps are: boot system, let it rest for 15-20min, load up K17TK, set FID to 38.0, apply, load SuperPi)
CPU-Z reads it correctly, but Task Man seems to think 38.0 multi = 3.3GHz (power plan is set to 100% Min/Max, so it generally reads 3.9GHz due to Boost)
EDIT2: At 37.75x I just posted a time of 8m 59.619s. Iinitial was 6s flat, Loop 1: 24.533, Loop 2: 45.644.
Running it again @ 38.25x. Initial: 6.813s, Loop 1: 26.205, Loop 2: 48.269. And just keeps getting worse.
LITERALLY all I did in between runs was use SnippingTool to take a quick screenshot of the times to compare, changed the FID (K17TK was still running), and started the run. I never really understood why Pi runs have such a huge margin of error. Doesn't make running it very fun when it's so damned inconsistent lol I'm afraid if I fart, it's going to tack on another 30seconds!
Aaand 9m 7.526s on this run, at 50MHz faster :|
Last edited by Formula350; 06-07-2017 at 05:48 PM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks