QuickMag now has a website: Estimate CPU/GPU performance for Gridcoin online

in #gridcoin6 years ago (edited)

http://quickmag.ml

The website allows users who do not have bash on their own computer to obtain estimated Gridcoin performance data for their hardware.

This uses the same scripts as described in:

What does QuickMag do?

The program works by finding the top hosts on each project with the specified model of CPU/GPU.
The number of whitelisted projects is obtained from gridcoinstats.eu and used to determine how much total magnitude is allocated to each project. This number excludes greylisted projects, even if they are still included in the results of this script.
The RAC for the top hosts are then divided by the RAC for team gridcoin and multiplied by the total magnitude for the project. This gives the magnitude awarded to each of the top hosts.

QuickMag returns a list of magnitudes and not an average, because there is no easy way to handle the statistics. Depending on the popularity of the CPU/GPU model, there may only be one or two people working on a particular project. This and some other intricacies result in the mean values being misleading and that you should look for multiple hosts with similar performance.

About the website

QuickMag is now available online: http://quickmag.ml

This website essentially allows you to run QuickMag on the “server.”
First select whether you are calculating performance for a CPU or a GPU. Then enter the name of the CPU/GPU.

The CPU/GPU name follows the same formatting rules as the QuickMag script. Links to the example names are provided. Note that spaces need to be preserved, for example 'i7-6700' will return a mix of 'i7-6700 ' and 'i7-6700K' results.

Other Notes

There are a lot of improvements to be made to the website. It does not currently recycle results, it only updates the host data once a week, and it can only handle a few simultaneous calculations.

If you want to submit a bunch of requests, download the scripts and run it on your own machine, it will be much faster.

smallGRCopt.png

Sort:  

Nice work!

Just noticed, when I search 'ARMv7 Processor rev 5 (v7l)' there is no results, only for 'ARMv7 Processor rev 5'. Brackets problem?

That's going to be because I have to be careful of special characters that could be put in the field that could be used to attack the site. I'll see what I can do to fix it.

edit: parenthesis are now allowed, this should fix the issue

It looks like the searches are case sensitive so be sure to format processor names in the same way as the example CPU and GPU lists show.

"gtx 660 ti" returned an empty result set but "GTX 660 Ti" worked for me.

It is definitely case sensitive. I'll see about adding an option to check for part names to make it easier/faster to get the right name.

edit: I removed case sensitivity for now. Other improvements will have to wait until later.

I think a drop-down option with different segments for each larger processor type (IE: i7, then a list of the i7 chips when you click on i7) would help. Other than that, I like seeing calculators like this so people who are more profit-minded don't avoid Gridcoin!

I like that idea, it would probably be a significant improvement over the current UI.
I'll see what I can do to implement it.

@nexusprime I got bored and started to redesign your UI, so I can try and implement that idea. Here's where I am currently at:
2222.png
do you have any way that I can directly contact you?

The ideal would be to have it pre-fetched

I think maybe it should also tell you the average mag calculated from all the hosts instead of just the top 4. And since you stated that performance data only updates on Fridays maybe data already calculated could be cached to greatly reduce the time required to fetch results?

Unfortunately, due RAC being a weighted moving average, there is a long tail on the distribution for all the computers that have switched projects. At the current time, the only way to know if the top 4 computers are all actively crunching and the mean is valid is if someone looks at the data by hand. I've got some ideas on how to mitigate that, but I don't have time to implement it just yet.

I'm working on saving previous calculations. Right now I'm redoing how users submit their component name. Once the component names are standardized, recycling the old results should be mostly trivial.

Hi! I am a robot. I just upvoted you! Readers might be interested in similar content by the same author:
https://steemit.com/gridcoin/@nexusprime/cpuquickmag-estimate-cpu-performance-for-gridcoin

Congratulations @nexusprime! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

Award for the number of upvotes

Click on the badge to view your Board of Honor.
If you no longer want to receive notifications, reply to this comment with the word STOP

Do not miss the last post from @steemitboard:

SteemitBoard Ranking update - Resteem and Resteemed added

Support SteemitBoard's project! Vote for its witness and get one more award!

Congratulations @nexusprime! You received a personal award!

Happy Birthday! - You are on the Steem blockchain for 2 years!

You can view your badges on your Steem Board and compare to others on the Steem Ranking

Do not miss the last post from @steemitboard:

SteemitBoard - Witness Update
Vote for @Steemitboard as a witness to get one more award and increased upvotes!