Splave - Core i9 7980XE @ 5199.6MHz - 54sec 174ms GPUPI for CPU - 1B

[jpmboy]

when the change to a benchmark is major, if it does not preclude legacy hardware for compatibility issues (eg, requires an instruction set the hardware does not have) and you want to control the ballooning of the total benchmark count, then add it as a new ranking and freeze earlier version points.  No where near the impact of the recent change in the Bot point system.

11 hours ago, jpmboy said:

Make a shift date, freeze boints for versions before 3.3 and use 3.3 going forward.

** Mods may want to change the GPUPI Rules page, from V3.1+ (mandatory from March 9th, 2018)  to remove the "+" from the rules, or change to 3.1+ ... but not 3.3.  It is misleading as written since it puts no limit on the version, only a floor for the mandatory version.  When was the beta testing for 3.2?

Edited April 8, 2018 by jpmboy

[Mr.Scott]

45 minutes ago, jpmboy said:

When was the beta testing for 3.2?

There wasn't any. It was implemented just like 3.3 was.

[websmile]

@jpmboyGood luck at enforcing this. When people say they want to preserve their work it is also globals (this is all about boints, seems no one cares for database integrity and comparability of results anymore), and you cannot give wr or global boints to an inactive retired benchmark. Point two, what about people who want even chances and get 3,2 and before points as well? If you cannot submit anymore to a benchmark you give longer active benchers a card blanche that others might never be able to make up for. Ergo, you need to retire it completely and strip points if you freeze points sooner or later...