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

LAR_Systems

Member
  • Content Count

    590
  • Joined

  • Last visited

Awards

1 Follower

About LAR_Systems

  • Title
    Member
  • Birthday July 12

Contact Methods

Profile Information

  • Location
    Oh Canada!
  • Gender
    Male
  • Interests
    Pretty much all things tech, Development, PC Building, Gaming, Aruduio, RPI, 3D Modeling & Printing, with the occasional building stuff with wood.
  • Biography
    Was prescribed a Vic 20 as a kid by a legit doctor to improve my hand eye co-ordination, the rest is history.
  • Occupation
    Solving whatever tech issue my clients have.

System

  • CPU
    2950X
  • Motherboard
    X399 AORUS PRO
  • RAM
    64 GB
  • GPU
    RTX 2080 Super
  • Case
    Phanteks P600S
  • Storage
    6TB NVME - 36 TB HDD
  • PSU
    Corsair RM 850
  • Display(s)
    Acer Predator 34in
  • Cooling
    Noctua Everything
  • Keyboard
    Kinesis Gaming
  • Mouse
    Logitech MX Master 2S
  • Sound
    Onboard
  • Operating System
    Windows 10 Pro
  • Laptop
    Lenovo X1 Carbon

Recent Profile Visitors

1,169 profile views
  1. 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
  2. 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.
  3. Thanks for your support, makes a big difference on days like this when things are not going as planned.
  4. 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.
  5. 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.
  6. 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.
  7. 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
  8. 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.
  9. 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
  10. @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.
  11. 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/
  12. 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.
  13. 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
  14. Liquid metal then? We know it's good at shocking & shorting.
×