Jump to content

Welcome to ExtremeHW

Welcome to ExtremeHW, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of ExtremeHW by signing in or creating an account.

  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members.
  • Take advantage of site exclusive features.

zodac

Members
  • Posts

    101
  • Joined

  • Last visited

  • Days Won

    3

zodac last won the day on May 9

zodac had the most thanked content!

Reputation

115 Enjoys helping others

1 Follower

Personal

  • Location
    New Zealand

Distributed Computing

Recent Profile Visitors

273 profile views
  1. 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.
  2. Hi all. The daily/hourly/monthly stats for the team should now be working. Apologies to all inconvenienced rats.
  3. 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.
  4. Found the bug. It was very stupid. It's times like these I'm glad I didn't make the github link public.
  5. Yeah, very odd. I had to restart to fix something, but the next update it seemed to add random stats. Can't even see how those values were calculated since the initial stats and offsets for each user seems to be correct. Looking into it now, but worst case I'll delete the stats for the past 5-6 hours. We'll lose the hourly stats, but the points will be credited fine.
  6. I think this would be simple enough to implement. Currently, to calculate a team's points, I get a list of all points for a user and add them all up. Should be trivial to instead sort that list then truncate it to the top 28 (or however many days we choose). Would probably mess up the daily team stats, since I don't think it could reconcile the best 28 days for users across different days (the total stats are calculated on each update, but the daily/hourly stats are calculated and stored each day). So if you're OK with daily/hourly user and team stats showing all points, and the total stats only showing the top 28 days, I think it could be done quite easily.
  7. Just an FYI to everyone, I did have a little proof of concept that loaded all the GPU entries from LARS at the start of each month, and updated all the multipliers automatically. I didn't put it in the live system because wasn't sure if we wanted multipliers changing every month. Also, it gives no flexibility to allow for non-LARS GPUs to be added (wouldn't be hard to add, just needs more time). If it's a big hindrance, it's definitely something I could try and make time for. Hey, I just tested some updates on axihub myself. From what I can see, the updates are taking effect on the backend, but not updating on the UI (I'm new to website caching, so probably haven't set things up properly). If you do a SHIFT+F5 to refresh the page, the values should be updated. Let me know if that works. If so, I'll disable the caching for now so at least you can modify things a bit easier.
  8. Gotta beat my record. See you all in 2030.
  9. Final stats for the beta run, and appropriately it's Out Of Beta that win for July. Congrats again to @damric @u3b3rg33k @Supercrumpet May 2021 Results June 2021 Results We should be switching over the live competition in about 20 minutes when the stats reset, and I'll let @BWG update on that.
  10. If I get 2 for this post, I'll have a ratio over 1.0. Then I'll never need to post again. All done. From now on, all my replies will be edits in this post to preserve my status.
  11. Latest stats, sorry I can't do more atm.
  12. So great news. My ISP doesn't allow for port forwarding. So I spent all day configuring stuff for no good reason! Gonna call them on Monday, see if I can get a static IP address which should help, but just another delay.
  13. I can only use floppy disks, can you send me some?
  14. They're running on my machine, no issues there. But I've not been able to expose the site to the Internet, the stock modem I have isn't doing the port forwarding properly. I've got a better modem to replace it, just haven't had time. Might be able to this weekend, but can't promise anything. Worst case, I'll post the stats here during the week.
  15. So my computer is back up, but having trouble exposing it to the internet. The stock modem is pretty crappy. Will hopefully have some time this weekend to replace it and get this live again. But stats should be being collected again from now.
×
×
  • 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