(12-31-2015, 08:11 PM)MagicalGentleman Wrote: you should really refactor how clock speed affects the result by the way, One configuration I tried was 28 for a 10 tick clock and 23 for a 100 tick clock D:
Also, me and capo once came up with a cool way to benchmark cpus programmatically using a modified version of fibb and the following rules:
You have 2 number displays, 1 display shows the current fibb value and the other shows the amount of times fibb has overflowed.
every time you overflow, you must start counting from the beginning again obviously.
The benchmark would be recorded by examining how many cycles it takes to do x iterations of fibb overflow, and multiplying that by your clock speed. The lower the number the better.
this test shows basically how well a cpu can do maths operations while giving feedback to a user. It covers the basics pretty nicely i think.
LOL! I redid the math function, it's a negative quadratic now. You should see a CPU with a ~10 tick clock and 16 PECU rating go to a -63 PECU rating at 100 ticks
