Jump to content
HWBOT Community Forums

Adjustment for Global Points - Work in progress


Recommended Posts

  • Replies 313
  • Created
  • Last Reply

Top Posters In This Topic

Hmm Looking at R7 picture I am not sure that such version is good enough. Too low difference in points. I mean 1st place difference to 10th place which is relatively much easier is just 22,4 points. I am not sure if such difference is worth rerunning and pushing higher. I am more like a fan of leaving scaling system like it was in the past, just trying to apply 1.25 or 1.5 base for 3D.

 

The main test is the transformation from rank-based algorithm to percentage-based algorithm. Here's the explanation of why it's necessary. Then it includes the rough version of my latest post. I received a message from the developer we're moving to further performance testing, which is basically ensuring the scaling with all the rankings works fine. Once this is completely I can go back to the theory and verify if the algorithm works as intended.

 

Once that's verified I will update the thread here again with more detailed information and the community can check UAT and feedback on the points (max, min, scaling, etc). Once we have a general consensus on the forum and among staff, we'll do a full write-up of the change and post it in public. If the general consensus is positive too, we can set a date of deployment for Rev 7. Still a long way :).

 

As a preview, here is the 3DMark Vantage 1xGPU ranking on our test server. The main difference is the scaling of the points as they are determined not by which rank you have but by how far your score is off the top score. The scaling is very flat, but this is something we can address by tuning the various algorithm parameters :)

 

 

 

This is written 3 posts above your reply: "Oh, we also added one more parameter in the algorithm design to determine the weight of a benchmark. In short, this parameter will allow us to arbitrarily limit points of certain benchmarks that are over valued. I'm looking at you, XTU.".

 

I mean, I call XTU literally by its name ... :rolleyes:

Link to comment
Share on other sites

I know it's just a test but this is not how I recall the discussion went. Shouldn't there be a bonus for the top scores in addition to the %-score? I think top 10 should get a bonus for placing in the top ten. With some kind of slope like there is today. Otherwise it will just turn into scatterbenching and there is not enough incitament to push for the really high scores. Or push just ahead of one of your competitors... Ranking is still very important. Particularly in competitions. What other sport is based on how much you are beaten by the winner? It's all about position.

Link to comment
Share on other sites

I know it's just a test but this is not how I recall the discussion went. Shouldn't there be a bonus for the top scores in addition to the %-score? I think top 10 should get a bonus for placing in the top ten. With some kind of slope like there is today. Otherwise it will just turn into scatterbenching and there is not enough incitament to push for the really high scores. Or push just ahead of one of your competitors... Ranking is still very important. Particularly in competitions. What other sport is based on how much you are beaten by the winner? It's all about position.

 

Yes, there will be a bonus as presented in this post.

 

I just want to keep you guys updated on the progress. Please give us some time to make sure everything is working as intended ... :)

Link to comment
Share on other sites

  • 1 month later...

Another update from our side.

 

As you may have noticed, the past couple of months were very busy for us as we had to prepare for the World Tour events in Brazil, South Africa and France. It's a bit quieter for me in the next month, so I will be able to finish the R7 proposal.

 

Very recently you may have also noticed some problems with the HWBOT submit function. Especially those present at our last WT event will know. From what we gather based on the server logs and reports, the issues are due to the way R6 is designed and our database structure. Once a heavy load action is ongoing on our database, the MySQL database locks all impacted rows until all queries are completely finished. The R6 calculation method requires all results in a certain global or hardware ranking to be updated. As I mentioned earlier in the thread, updating one result affects other update query triggers such as updating the User Total, the League Ranking, Notifications, Achievements, etc.

 

I hate to say this again, but with XTU throwing so much data at our servers it's not surprising the current calculation method is stretching our servers. To give you a figure, in January alone we had to process 80,000 data requests from XTU.

 

The calculation method for R7 will reduce the transaction load by a great margin, luckily.

Link to comment
Share on other sites

Hah, I'm not sure if "less submissions" is the best approach here. The large quantity is a good thing. :)

 

What R7 is about is reducing the amount of updaters being triggered per submission so that a large quantity of submission doesn't end up locking the database for too long.

Link to comment
Share on other sites

  • 2 weeks later...

Making a bit more progress. I've asked the developer to move the R7 test to a higher capacity server to have a fully calculated test server.

 

Below a comparison between R6 and R7 for the global ranking (+ WR points). What is implemented is:

  • Points are awarded based on relation of your score versus the top score
  • Participation threshold for maxPoints was lowered
  • For XTU we artificially reduced the points

You can see the effect of the XTU restriction by comparing it to the HWBOT Prime points. Note that the Fire Strike 4xGPU and XTU 8xCPU category also has WR points included.

 

attachment.php?attachmentid=4152&stc=1&d=1460876138

 

Below are screenshot comparisons for the Hardware Points:

  • SuperPI 32M 2600K: R6 vs R7
  • Fire Strike GTX 970: R6 vs R7
  • XTU 6700K: R6 vs R7

Link to comment
Share on other sites

Thanks for the update. Nice to see things are moving along.

I would appreciate if you could define what the goals are for this update. I know about the load on the servers, and XTU points. But what else?

 

Some thoughts on the figures above:

- WR points should be decreased since the global points are higher now.

- Why artificially limit XTU, why not a cap for maximum number of scores that affect all benchmarks the same?

- Points scaling seem better, but would need to see the whole deal to really know. Test server usually don't have all scores to give correct reading.

Link to comment
Share on other sites

It seems to be going in the correct direction (which benchmarks get more global points, example = SuperPi 32M), but I question how high some of the global points are. When points are too easy to get they individually seem worthless and might also detract from benching. If anybody understands what I'm getting at?

Edited by Noxinite
Link to comment
Share on other sites

  • 2 weeks later...

The latest points update seems a bit skewed for Maxxmem... idk tho lol. Getting #465 score globally and getting nearly 72 points for it seems like a lot... Then again, maybe not. I was just a bit surprised to see 760 points on uat when I have 140 on the live server :P

attached is my global points as of this post

 

 

also, seems really cool with the updates you are working on for points. Hopefully you can end up on one that is fair and also not skewed to certain benches like xtu or others.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...