HWBoints Revision 7 Overview

  • News, Articles
  • 4
  • HWBOT

HWBoints Revision 7 Overview

Revision 7 is designed in response to community feedback with the intent of awarding points more accurately as a reflection of overclocking result quality. The new revision re-balances the weight of benchmark applications and awards points based on result quality relative to the top result.
 

Contents

Join the discussion on the forums here: http://forum.hwbot.org/showthread.php?t=150289
 

Background Information

At the core of the HWBoints concept, invented by Mtzki from Finland, lie two distinct parameters: the weight of a ranking as determined by the amount of participants, and the quality of the result as determined by its position within the ranking. This concept is now being stretched to the end of its scaling capabilities due to two primary reasons: 1) the increase of global and hardware rankings, and 2) the direct submission capability of benchmark applications via our Open API.

To explain the first point, consider the following comparison of the database state in 2006 with 2016. As you can see below, the amount of data our servers need to process has grown spectacularly.

  • Submissions: 20,000 vs 1,644,000
  • Users: 1,270 vs 72,000
  • Teams: 200 vs 2,200
  • CPUs: 400 vs 3,000
  • GPUs: 230 vs 1,650
  • Benchmarks: 14 vs 102

 
To explain the second point, we need to shed some light on the cooperation with Intel since June 2013. Using the Open API functionality we developed for HWBOT Prime, the benchmark integrated in the Intel Extreme Tuning Utility allows enthusiasts to directly submit to the HWBOT database. Its inception turned out incredibly successful as almost 370,000 submissions have been made since. As a result of its popularity among general enthusiasts, the XTU Global rankings have the highest participation ratings among all benchmark applications. For example, the 4xCPU ranking for quad-cores has 37,000 users participating. Since points are awarded based on the popularity of a given ranking, XTU submissions generate the most amount of points.

This conflicts with the overclocking community’s desire to have the Overclockers League and submission points reflect the skill and effort required to achieve the position. Revision 7 addresses these concerns.

There is a PDF version of this article available for download: pointsGlobal v1.0 public
 

Previous HWBoint Revisions

Below an overview of the HWBOT revisions which feature HWBoint changes.

 

R7 Major Goals

The major goals set out for Revision 7 include addressing community concerns, as well as addressing server constraints. The major goals are to:

  • Re-assess the impact of benchmarks with API submissions
  • Re-assess the value of 3D benchmarks
  • Reduce the server impact of point calculations

 

The Algorithm: Theory

The algorithm is,
 

R7 Algorithm 1

R7 Algorithm 2

R7 Algorithm 3


 
With ,

  • A, B, C, X, Y, Z = Scaling parameters
  • P1 = Top score in ranking
  • PX = Score in ranking
  • U = Users in ranking
  • Umax = Limit for users in ranking
  • Pmin = Minimum required performance for points
  • PTmin = Minimum points for a type
  • PTbonus = Bonus points for a type
  • APPmp = Application multiplier

 
The point algorithm is used to determine the value of a submission on three different levels (or types):

  • HP = Hardware Points, based on benchmark, CPU or GPU (per core count)
    • I.e. 3DMark05 with 2x GeForce GTX 480
  • GP = Global Points, based on benchmark per core count
    • I.e. 3DMark05 with 2xGPU
  • BP = Benchmark Points, based on benchmark

 
Each type of points has a different set of parameters and restrictions. Find the details below:

TypePTminUmaxPminPTbonus (U > 10)PTbonus (U <= 10)
BP150000.9#1#1#3#4#5#1#2#3#4#5
7510302010108642
GP110000.5#1#1#3#4#5#1#2#3#4#5
7552010554321
HP0.12000.75#1#1#3#4#5#1#2#3#4#5
10220021.500

 

The Algorithm: Practical

For those less familiar with mathematics, a bit more information below. On our test environment you can find the R7 algorithm in action. The link is: http://uat.hwbot.org/.
 

Improve your points

Just like in all previous revisions, the best way to improve your Benchmark, Global and Hardware points is by improving your overclocking result. Because the R7 algorithm is based on your performance relative to the top score, improving your result will always improve the points contributed to the score. Regardless of a change in position within the ranking.

As the leader of a ranking, you can extend your lead over the competition by improving your score. As you create a wider gap between your top score and the others, the points of other results will decrease.
 

Maximum Points

The maximum points for each Benchmark, Global and Hardware ranking is governed by three arbitrary parameters: Umax, APPmp and PTbonus. Umax determines the cut off for the amount of participants impacting the points. APPmp is a multiplier which affects the final base points and can be used to increase or reduce weight of certain benchmarks. PTbonus is used to offset the top scores from the algorithm as it adds points to the top-5 places.

The maximum points for each ranking is:

  • Benchmark Points: 176.5 points
  • Global Points: 161.6 points
  • Hardware Points: 53.8 points

 

Minimum Points

The minimum points for each Benchmark, Global and Hardware ranking is governed by four arbitrary parameters: Pmin, PTmin, PTbonus and APPmp. Pmin is the minimum performance percentage required to score points in the ranking. If your score is less than this performance cut off, it receives no points. PTmin determines the lowest points awarded in a ranking. APPmp is a multiplier which affects the final base points and can be used to increase or reduce the weight of certain benchmarks. A special table of PTbonus is used for low participation rankings and defines the points awarded in cases where the number of the amount of participating users is less or equal to ten.

The minimum points for each ranking is:

  • Benchmark Points: 1 point
  • Global Points: 1 point
  • Hardware Points: 0.1 point

 

Community Decisions

The algorithm allows for the community to increase or reduce the emphasis of specific aspects of overclocking. Although all parameters are arbitrarily set, it is recommended to only change the following parameters:

  • BP/GP/HP: enable/disable points
  • APPmp: percentage of base points, affects all rankings of a benchmark
  • PTbonus: offset top-5 bonus points
  • Pmin: adjust minimum performance required for points

In the current implementation, the APPmp is configured to 1.00 for all benchmarks except for the CPU benchmarks which are configured to 0.80.
 

OC-ESPORTS Competition Points

The OC-ESPORTS Competition Points are not governed by the HWBoints algorithm but are awarded based on a fixed distribution. We mention it briefly as it is relevant to the next section of the document.

We distinguish three levels of competition, appropriately named Level 1, 2, and 3.

Level 1 includes online overclocking competitions such as the HWBOT Country Cup or sponsored competitions. It also includes our Road To Pro Challenger and Pro OC Divisions. Lastly, it also includes invitational live competitions. Level 2 is for live competitions only. We include live qualifiers for a world final and regional finals. Level 3 includes only the global live competitions. Note that Level 2 and Level 3 only applies to open live overclocking tournaments.

Each of the levels has its own point structure. For winning a Level 1 competition, you receive 50 points. For winning a Level 2 competition, you receive 100 points. For winning a Level 3 competition, you receive 250 points. For participating in a Level 1, 2, or 3 competition you receive respectively 1, 10, and 25 points. You can find a complete table at the bottom of the article.

For each competition you can only earn points once. That means the maximum points a Level 1 competition can contribute to your ranking is 50, regardless of the amount of stage won.

For team, country, and competition team based competitions such as (respectively) the Team Cup, Country Cup and Pro OC, each member of the team, country, or competition team participating in the competition receives the same amount of points. Taking Australia as an example, for winning the Country Cup 2014 each of the participating Australian overclockers receives 50 points for winning the online competition.

You can find more details on the distribution at OC-ESPORTS.io: http://oc-esports.io/#!/rankings-details.

 

League Algorithms

 

Overclockers League

The league algorithm is similar to R6 with a couple of tweaks. In the equation below you can find the calculation for points in the Overclockers League.
 

User Points

 
Where,

  • A = Top 15
  • B = Top 40
  • C = Top 25
  • BP = Benchmark Points
  • GP = Global Points
  • HP = Hardware Points
  • CP = OC-ESPORTS Competition Points

Compared to Revision 6, we have increased the allocation of Hardware Points from 30 to 40.

In addition we have also addressed the issue of “double-dipping”. In the past, a single score could yield points for both BP/GP and HP, resulting in a double-dip boost. In Revision 7, a score will yield either BP/GP or HP (whichever is higher).

On our test environment the Overclockers League employs the R7 algorithm.
 

Teams League

The League algorithm is identical to R6. In the equation below you can find the calculation for the point in the Teams League.
 

Team Points

 
Where,

  • GTPP = Global Team Power Points
  • HTPP = Hardware Team Power Points
  • UP = User Points (all BP, GP and HP of team member)

On our test environment the Overclockers League employs the R6 algorithm. It does not reflect the adjustments of R7!
 

Hardware Masters

The League algorithm is identical to R6. In the equation below you can find the calculation for the point in the Teams League.
 

Hardware Masters Points

 
Where,

  • HP = Hardware Points

On our test environment the Overclockers League employs the R7 algorithm.
 

Distribution Graphs: Theoretical Example

In the distribution graphs below you can find the theoretical distribution of points for a ranking with evenly distributed scores.

R7 Theory: Benchmark Points R7 Theory: Hardware Points R7 Theory: Global Points
(clickable)

 

Distribution Graphs: Real World Example

In the distribution graphs below you can find real world examples of the distribution of points for a specific ranking. The rankings used are:

  • Benchmark Points: 3DMark Fire Strike
  • Global Points: 3DMark Fire Strike 1xGPU
  • Hardware Points: 3DMark Fire Strike 1x GeForce GTX 970

R7 Real-World: Hardware Points R7 Real-World: Global Points R7 Real-World: Benchmark Points
(clickable)


4

Belgium Massman says:

Let's continue the discussion in the original R7 thread: http://forum.hwbot.org/showthread.php?t=150289

Czech Republic buildzoid says:

The real world example graphs look like there will be lots of people with no points on many of their scores. Or am I reading those wrong?

Australia zeropluszero says:

When is this expected to be implemented?

Belgium leeghoofd says:

As soon as Neil hits nr 1 spot

Please log in or register to comment.

Leave a Reply: (BBCODE allowed: [B], [QUOTE], [I], [URL], [IMG],...)