Jump to content

Welcome to ExtremeHW

Welcome to ExtremeHW, register to take part in our community, don't worry this is a simple FREE process that requires minimal information for you to signup.

 

Registered users can: 

  • Start new topics and reply to others.
  • Show off your PC using our Rig Creator feature.
  • Subscribe to topics and forums to get updates.
  • Get your own profile page to customize.
  • Send personal messages to other members.
  • Take advantage of site exclusive features.
  • Upgrade to Premium to unlock additional sites features.

zodac

Members
  • Posts

    113
  • Joined

  • Last visited

  • Days Won

    5
  • Feedback

    0%

zodac last won the day on October 11 2021

zodac had the most thanked content!

Reputation

149 Enjoys helping others

1 Follower

Personal

  • Location
    New Zealand

Distributed Computing

  • Folding@Home
    zodac

Recent Profile Visitors

3,954 profile views

My Awards

  1. Hi everyone, Been a while since I've made an update, but there's a new feature coming to the site later today (live now!). I've added the ability for users to request some common changes directly through the site, rather than needing to go through @BWG/ @damric. You'll see a new option on the navigation bar, at System> Request A User Change From here, you can request a change for: Your Folding@Home username Your passkey Your live stats link (if you have one) Your hardware Note: You will need to enter the existing passkey first, to avoid anyone requesting changes for someone else. You can also request the change to made ASAP, or schedule it for the start of next month. Once the request is made, please send a PM to @damric, and they'll review it and approve (assuming they're happy with the change). Pinging the captains so they're aware. @BWG @CharliesTheMan @damric @firedfly @Supercrumpet@tictoc
  2. I think that was before I took over actually, the milestone badges were there before me. I think it was mortimersnerd who was in charge back when I joined. But I'll happy take credit. I actually only got involved with the community because I was rocking a Pentium D at the time, which was good for ~150 PPD. No job either, so was stuck on that for a couple years until people felt I was embarrassing them and got me some better parts. So I spent time convincing other people instead and just made a lot of guides. I kept all the screenshots too! And a few plans for other events that I sadly never got around to. Then I was asked to take over, and started running events. Restarted the TC with help from a lot of other people. Had a lot of fun for a couple of years, but man, did I lose out on sleep and then I nearly failed my uni course. Huge arguments with other forums whenever the Chimp Challenge came around. Lost a few people in the community too. Eventually took a step back and let people like @BWG and @axipher get involved. Now I'm far more casual, but the numbers have skyrocketed so much, feels like I'm just a drop in the ocean. Nice to hang out and chat with folk though. Plus working on the ETF site gives me something to procrastinate on for my actual job.
  3. Why are you idiots when you're asking the *real* questions?
  4. Yup, nice and secure now. If anyone is updating bookmarks, use the https://etf.axihub.ca link, might get rid of the other one at some point and only use ETF going forward.
  5. Hi all, The stats site may be unavailable/broken for a few hours, just changing some internal links around and it might take some time to propagate out.
  6. Hey all. As promised, the LARS automation work is basically done and will be turned on for November. Here's the output of the multiplier changes if I was to run it right now on the existing hardware, for reference. @BWG wildfly_dev | Best PPD is '6,643,151' wildfly_dev | 212 from LARS, 15 in DB, 15 to update wildfly_dev | Updated hardware 'Navi 10 [Radeon RX 5600 OEM/5600 XT/5700/5700 XT]' (ID: 46), multiplier: 5.07 -> 4.7, average PPD: 1301320 -> 1413961 wildfly_dev | Updated hardware 'TU104 [GeForce RTX 2080 Super]' (ID: 55), multiplier: 2.48 -> 2.6, average PPD: 2693818 -> 2552709 wildfly_dev | Updated hardware 'GP107GL [Quadro P620]' (ID: 40), multiplier: 48.13 -> 49.5, average PPD: 138084 -> 134216 wildfly_dev | Updated hardware 'GM204 [GeForce GTX 980] 4612' (ID: 24), multiplier: 8.76 -> 7.86, average PPD: 771118 -> 845108 wildfly_dev | Updated hardware 'GM107 [GeForce GTX 750] 1111' (ID: 41), multiplier: 97.13 -> 96.45, average PPD: 68879 -> 68879 wildfly_dev | Updated hardware 'Vega 20 [Radeon VII]' (ID: 56), multiplier: 3.33 -> 3.31, average PPD: 2008233 -> 2008233 wildfly_dev | Updated hardware 'GM206 [GeForce GTX 960] 2308' (ID: 57), multiplier: 21.3 -> 20.64, average PPD: 314056 -> 321821 wildfly_dev | Updated hardware 'GK104 [Quadro K5000]' (ID: 45), multiplier: 61.27 -> 60.84, average PPD: 109196 -> 109196 wildfly_dev | Updated hardware 'TU102 [GeForce RTX 2080 Ti Rev. A] M 13448' (ID: 48), multiplier: 1.32 -> 1.5, average PPD: 4960313 -> 4430496 wildfly_dev | Updated hardware 'TU106 [GeForce RTX 2070 Rev. A] M 7465' (ID: 50), multiplier: 2.71 -> 2.7, average PPD: 2448739 -> 2463563 wildfly_dev | Updated hardware 'GM204 [GeForce GTX 970] 3494' (ID: 21), multiplier: 12.97 -> 13.44, average PPD: 511994 -> 494421 wildfly_dev | Updated hardware 'Ellesmere XT [Radeon RX 470/480/570/580/590]' (ID: 42), multiplier: 12.91 -> 13.49, average PPD: 519263 -> 492376 wildfly_dev | Updated hardware 'GP104 [GeForce GTX 1070 Ti] 8186' (ID: 51), multiplier: 4.78 -> 4.74, average PPD: 1399391 -> 1400077 wildfly_dev | Updated hardware 'GM107GL [GRID M40]' (ID: 54), multiplier: 14.51 -> 57.64, average PPD: 115244 -> 115244 wildfly_dev | Updated hardware 'raven [Radeon RX Vega gfx902]' (ID: 53), multiplier: 153.94 -> 115.05, average PPD: 44057 -> 57743
  7. Yeah, axihub was down for a few hours and inaccessible. Seems to be back online now though.
  8. Hey all, just an update on some of the LARS automation work. I've got most of the bits running locally now, and I think it should be ready to go live by the end of the week. The plan is to run it once a month, so after the stats are reset, and in the two days downtime before the stats start up again. However, it does seem that there is some fluctuation with the PPD values which can look suspicious/out of sync. @BWG has already manually updated the multipliers for October, and me checking 8 hours later has shown some small differences. To prevent any concerns, I'm going to update the list of hardware (available here) to include the average PPD and multiplier. The plan is to update all hardware values at once, so going forward you can consider the values here to be a snapshot of the PPDs for the upcoming month. It would be far too much effort to update more frequently than monthly, so I hope this is a fair compromise. There are some PPD values up on that page now, but since we don't have the #1 hardware, there is nothing to compare it to. It will be there next month and you'll be able to compare yourselves if necessary. I'll update here again once I have something running/tested locally, but you won't see any updated multipliers/PPD on the live stats site until November.
  9. Done, check the results page and the stats should all be there now.
  10. I have all the old stats, so I should be able to do this. I just haven't had the time. I will get to it, I promise!
  11. Huzzah, the September results were saved correctly! http://teamcomp.axihub.ca/results.html
  12. Hi all, I've added a new link to the nav bar on the UI to show past results. This will show the final result of each month, and avoid it needing to be retrieved in the small time window between end of one month and the start of the next month (about 20 minutes). Apologies for not having it ready for end of August, the last week or so has been a bit rough. It will be empty for now, but I've tested it manually. We'll know for definite how it works at the end of this month though.
  13. Hi all. The daily/hourly/monthly stats for the team should now be working. Apologies to all inconvenienced rats.
  14. Basically, when we restart the container, I load all the offsets for each user from the DB into an in-memory cache. I do this for various bits of info so I'm not hitting the DB for stuff that only changes very infrequently. I somehow forgot to filter my DB query by user, so instead every user was given the same offset. It only occurred now because I restarted the container to apply a different fix. When a new offset is added, it's added to the cache first, so the retrieval query to the DB wasn't ever used. Small silly thing, and we didn't have many offsets during the beta run, so just didn't come up.
×
×
  • Create New...

Important Information

This Website may place and access certain Cookies on your computer. ExtremeHW uses Cookies to improve your experience of using the Website and to improve our range of products and services. ExtremeHW has carefully chosen these Cookies and has taken steps to ensure that your privacy is protected and respected at all times. All Cookies used by this Website are used in accordance with current UK and EU Cookie Law. For more information please see our Privacy Policy