32m Low Clock Challenge

[corvus_corax]

13m 26.047s @ 3.6GHz
Just a slightly tweaked system and using sabinu's tweak (pseudo-minimize tweak, that explains SPi right align Thanks man :thumbsup: ).


Edit: A better shot

Well, here is before edit
13m 29.078s Monitor

[alpha0ne]

13m 29.078s @ 3.6GHz[/url]
Just a slightly tweaked system and using sabinu's tweak (pseudo-minimize tweak, that explains SPi right align Thanks man :thumbsup: ).

Brilliant time

Care to explain these pseudo-minimize tweak, that explains SPi right align ???

[corvus_corax]

Brilliant time

Care to explain these pseudo-minimize tweak, that explains SPi right align ???

Thanks alpha0ne
About pseudo-minimize, here sabinus explains the tweak:

It's been a while since last tweaks were posted here.
Now I want to tell about one tweak that did help. It doesn't compare to copy-waza in terms of time gain but it gave me around ~0.1" for 1 MB SuperPI runs. Because of the nature of this tweak I think it is more helpful to 1 MB / 2MB runs then for 32 MB runs.
I call this tweak: pseudo-minimize because it resembles to minimize but it's not the same. It goes like this:

When all other tweaks are done (including realtime priority and copy-waza) and you are ready to launch SuperPI 1MB, then drag the bottom-right corner of the SuperPI window towards the upper-left corner untill the only thing left visible remains the small title bar of the window.

Then use the keyboard to launch SuperPI with the combination ALT+C then select the desired run (1MB, 2MB etc) with either the keyboard or mouse, then hit Enter (or click OK).

Finally, when the "PI calculation done!" message appears you should put the mouse pointer over the TaskBar, click the right button and select "Tile Windows Vertically" to see the whole SuperPI window and do the screeny fest

Useful for 32M too

[dinos22]

you are still missing the point people

i don't know how many times it needs to be repeated..............the idea is to get into the sub 13m/14m/15m etc times with lowest possible CPU MHz

so when you submit your time for sub 13m run the idea is to get to score around 12m 55-59.99s times with lowest possible CPU MHz.......for corvus that would mean raising the CPU MHz to lower the times from 13m 29s to JUST UNDER 13m

[funkflix]

Sorry for missing the topic again, but maybe anyone of u guys can tell me, why my 32M times that bad?!

I tried Win2k3/WinXP with realtime and without and different ramclocks, both on clean windows. Normally i should go easy into the 13min imho, even without tweaked windows, but i just can get around 14min..



Vcore 1,53V
Vdimm 2,4V

Any ideas?

[dinos22]

Sorry for missing the topic again, but maybe anyone of u guys can tell me, why my 32M times that bad?!

I tried Win2k3/WinXP with realtime and without and different ramclocks, both on clean windows. Normally i should go easy into the 13min imho, even without tweaked windows, but i just can get around 14min..



Vcore 1,53V
Vdimm 2,4V

Any ideas?

maybe create a new thread

just from initial things i'd say it's the 1333 that's hurting you badly there

[funkflix]

maybe create a new thread

just from initial things i'd say it's the 1333 that's hurting you badly there

I'm not the guy who is creating new threads all the time. It's even more realistic to get fast and good help into here.

Anyway, thx or ur answer, but look at bachus results a few pages before, he had 12min 59s with 3600MHz!? U think the strap is that important for 32M, that i can not even hit this time with + 4000MHz?

[alpha0ne]

you are still missing the point people

i don't know how many times it needs to be repeated..............the idea is to get into the sub 13m/14m/15m etc times with lowest possible CPU MHz

so when you submit your time for sub 13m run the idea is to get to score around 12m 55-59.99s times with lowest possible CPU MHz.......for corvus that would mean raising the CPU MHz to lower the times from 13m 29s to JUST UNDER 13m

Hehehe thanks for bringing that up again dinos, ppl were posting +4GHz runs