Folding Forum

Thus my suggestion to not mess about with affinity Agreed. It's fine for a dedicated folding machine or for someone who's willing to risk their browser slowing down a bit, but the average person should not be messing with it. A single person accidentally pinning two threads to one core would undo t...

Few percent is margin of error. Not worth potentially messing up stability. It is always advised to leave things as they are and let Linux scheduler do it's job. Especially when you are doing mission critical workloads. I am certain the people who maintain the scheduler side of things have much bet...

And while I'm at it, a question for Arisu. What is the standard memory clock on that 5070 mobile you have? It just seems like a huge bump in clocks, and I hadn't seen people pushing the 5000 series GPU's that far on memory. As for core clocks.... well they have plenty of overhead for sure. I haven'...

Just for input - Myself and a couple others have found that lowering the memory clocks is actually more efficient. I haven't seen any testing on newere hardware, but the idea is that anything since Turing has more than enough memory bandwidth and there is little if anything to be gained. BUT drivin...

You can also increase the memory clock, which is useful for very large WUs (many atoms) and most GPUs handle it far better. The actual values for both shader and memory clock offsets varies not just for individual models, but for actual individual cards themselves. That is why the current values are...

Using AI to calculate an efficiency score, to compare performance per watt between devices, users, and teams. Why AI? Calculating power requirements has nothing to do with natural language processing. I have to note the irony of using something as energy-intensive as AI, boiling lakes and sucking u...

This happens frequently to me as well. AI scraper bots are hammering the site and basically DDoSing it, so this is the interim solution.

There are less invasive solutions like Anubis but the FAH team hasn't set that up and are only using Cloudflare.

There's another tip I forgot. Find the IRQ used by Nvidia by running this: # grep nvidia /proc/interrupts The first column is the IRQ. There may be more than one row. Take the top row's IRQ and pin it to the same core that you pinned the GPU parent thread to. So if it is IRQ 44 and the GPU parent th...

You don't absolutely need to set the GPU into EXCLUSIVE_PROCESS mode. It's just helpful so that you know that nothing is bypassing the MPS server. If your GPU is stuck in DEFAULT mode, don't worry about it.

Sadly I don't have a Linux machine to test it right now, but try running a WU with 4 threads, and pin them in the following configuration: thread 0 - cpu 0 thread 1 - cpu 1 thread 2 - cpu 2 thread 3 - cpu 2 You will quickly notice that threads 0 and 1 still keep using 100% of CPU time, although com...

After looking at this again, I think it doesn't matter. RDTSCP timings are used for DLB (Dynamic Load Balancing), which only matters on distributed systems that use multiple MPI ranks. FAH does not currently use multiple MPI ranks, so it probably gets no benefit from better timings. The timings are ...

It does help, thank you. I'm surprised that the bandwidth is so low. I will test my system with different driver versions to see if it might be a driver issue.

The shortage is temporary and there are no plans to explicitly require 4 threads. Even the requirement of 3 threads is simply a temporary workaround due to a bug in the client that only happens on systems with 2 threads.

I decided to try out a 5090 on Windows. I set the power level as low as I could, which was 66%, so it runs around 400W. Seems to consistently get WU's, but sometimes the PPD will say 40-45M, where other times it's more like 20-25M, depending on the WU. I guess that's where Linux could come in handy...

Try restarting the clients directly with "sudo systemctl restart fah-client". Sometimes that is necessary.