Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

LAR_Systems

Member
  • Content Count

    598
  • Joined

  • Last visited

Everything posted by LAR_Systems

  1. To add too this, users that lower power settings for their card to save money folding. The Facepalm of people I see trying to fold using old mining rigs on 1X risers. Combine these with any of the above and brutal PPD.
  2. They botched the rollout... it broke the APIs of the web clinets and other integrations... they need to account for the legacy systems then try again would be my guess.
  3. Points scores etc. all come out of the F@H core client I have no say in their calculation, reward etc. I capture samples of the data reported by F@H during folds to be averaged and they fluctuate up and down while folding, they are never 100% consistent, you can see that in the charting view in the client. This means you can not really look at how your card is folding right now on a specific Work Unit PRCG and have it be 100% match of the average for the project/gpu as each WU PRCG will fold differently day to day or within the folds inside the work unit, which is w
  4. A patch has already been pushed to account for their changes Monday morning. When they did their initial update on the weekend they broke the stats / user API URLs for both clients. We applied a hotfix to get around the issue fixing it in the dark mode extension, looks like they have restored the originals finally. You need to update the extension to version 1.1.4. to see the update. Cheers
  5. Don't know what you are referring to regarding points. But I'm gonna say no, what I'm talking about is F@H orphaned some APIs their web clients use to show your total points and project descriptions. Has nothing to do with the folding engine, card performance or folding cores.
  6. @marknd59 @RollinLower I have pushed a work around for F@H in the dark to point to legacy APIs at F@H to restore the functionality of points, project etc. in my client. They have not yet fixed redirects or replacement of these APIs with their new page launches so the default web client they ship is broken. I'm also seeing the issue with little to no work on the WS or long waits for it. Hopefully they are working through the issues today. Anyways... if you force update of F@H INTD to v 1.1.4 you get most of the functionality back. Wait and see until / how they are going to fix
  7. It's not on the F@H In the Dark end... F@H appears to have broken a number of APIs and possibly the work servers.
  8. Looks like F@H is in the middle of a server and API upgrade and may have broken a little bit of everything? Is F@H working for anyone else or no?
  9. LAR_Systems

    Hey, can you update the badge eligibility on th…

    Hi there, it has been updated and should push out over the next 24 hours to users as their clients reset. Sorry for the delay in response.
  10. Hi all, quick update for today! For those that have not found it already, information on the site for GPUs now shows the average PPD and the separate Windows & Linux PPD averages with this more detailed information also being send to the web client so the WU Reward indicators are more fair based on the OS you're running. The web client has also had the default Start / Stop functionality stripped in favor or direct buttons that just do what you expect them to without the popup window first. For users running F@H 7.6.14 or higher this also adds a dedicated Finish button
  11. I'm going to say this was a change in Brave as the client update was little more than a refresh for the benefit of the google approval team. I would not be surprised given the purpose of the Brave browser that they don't like all the things with the way F@H browser stuff talks to the localhost / IP on a non standard port per the way the F@H service works. That all said, I do really appreciate the additional CPU samples.
  12. Thanks for your support, makes a big difference on days like this when things are not going as planned.
  13. FYI: Google has changed the way they review the extension sometime around 12AM EST today and therefore I have to resubmit it updated. It has to do with the CPU tracking feature, they are suggesting the app does not use the CPU permission, and you can't have an app that asks for permissions it does not use... meanwhile it showing CPU names, logical processors and their PPD suggests otherwise. I assume it's a matter of review automation not being able to tell how it's used, and it's hopefully resolved quickly. Kinds feeling like Luc with floatplane app fun right now.
  14. I know there was some talk that F@H was trying to improve on the work servers giving specific GPUs WUs they are best suited for. Wonder if this is that given the consistency.
  15. Google has changed the way they review the extension sometime around 12AM EST today and therefore I have to resubmit it updated. It has to do with the CPU tracking feature, they are suggesting the app does not use the CPU permission, and you can't have an app that asks for permissions it does not use... meanwhile it showing CPU names, logical processors and their PPD suggests otherwise. I assume it's a matter of review automation not being able to tell how it's used, and it's hopefully resolved quickly. Kinds feeling like Luc with floatplane app fun right now.
  16. Question for all of you: Has anyone been able to install the RPI F@H client? Been trying to get the package to install on a RPI 4 for testing and have not been able to get the package to complete install. I assume F@H project resources are pretty light on this, so wondering if it's just my latest build of Raspbian that's the issue, or if anyone has gotten it working. Thanks
  17. This is likely the projects your getting are performing better on your GPU. Been getting some reports that people are seeing higher PPD on projects that previously did not perform very well. So enjoy the ride, but if it's consistent across the F@H network others card will start creeping up in average as well.
  18. Hi, thanks for installing! Aside from what the others have said, Linux is better PPD, faster cards people tend to downclock... etc. Project 13428 has historically been a poor performing project on 30 series systems. What may have happened is F@H / Project team has modified the project WUs or bonuses as I can see these kinds of fluctuations in the data that are bigger than just normal daily adjustments. For the newer 30 series cards I know from what I'm running F@H is leaving a lot of GPU power on the table right now, so hopefully they are further optimizing work units f
  19. @chaozbandit is spot on. FAH is reporting it that way, I can’t do anything unless they break them up by bios / pci id. FAH tends to leave AMD cards grouped unfortunately.
  20. Hi All Version 2.0 of the https://folding.lar.systems/ PPD database site has just gone live. Along with some navigation, UX and overall template updates the 2.0 version launches the public version of the CPU PPD database and provides stats on the number of samples etc. available for devices when showing averages. GPU Database: https://folding.lar.systems/gpu_ppd/overall_ranks CPU Database: https://folding.lar.systems/cpu_ppd/overall_ranks These is also a simplified database for viewing active folding projects https://folding.lar.systems/projects/
  21. Remember, it could... but only if you had it only folding and were doing next to nothing else on the system. This is why I built a per logical core chart on the CPU profiles https://folding.lar.systems/cpu_ppd/brands/amd/folding_profile/amd_ryzen_9_5950x_16-core_processor so you can see how PPD might look at different logical core usage thanks to system overhead, GPU folding etc.
  22. I can say you have pushed this beyond my testing setup for sure. That said, looking at the slot IDs I think that would be the issue... they are not in order or sequential suggesting you have been adding and removing slots running up the ID number. Think in the live version of the client I only account for 8 slots with charting as 8 GPUs is pretty much the max config for a pretty baller system running 4X GPU lanes per card. Would suggest in the short term that you finish the slots... remove them all. Reset, add them back. You should get slots 1-6 which the charting
  23. Liquid metal then? We know it's good at shocking & shorting.
×