-
32M initial values + pi_rec.dat2 : update
guys, just a 'minor' update/correction to this, but the general behaviour is still the same.
my earlier pre-conditions for 32M initials are not correct: Pi size and time are both irrelevant.
i found that any result for any Pi size, if present in pi_rec.dat2 before SuperPi is opened, can reduce 32M initials by 0.5s.
re-tested with runs from 16K up to 32M and they all produced the same effect on 32M initials. Don't know if there is a threshold time for any particular Pi size, but i also tested @ 3Ghz with same results.
new tests/results:
for High 32M initial:
1) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), run 32M (High initial showing)
2) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), close Spi, open new Spi, run 32M (High initial showing)
3) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), run Pi size X, run 32M (High initial showing)
for Low 32M initial:
4) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), run Pi size X, close Spi, open new Spi, run 32M (Low initial showing)
doubtful that this was really a sensible use of time, but the aim for me was to find a consistent way to get one or other type of 32M initial

cheap
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