Favebook

Looks like Sidock's out for being hosted in Russia and thus not being accessible for the very active Ukrainian team, replacement probably announced on Sunday...

I've reached out to LMG to try to get another shout out and also jake is going to throw some hardware at the marathon 

I'm doing them all but 15e small numbers and 16e small numbers give the best points for run time. 16e small being the better of those two, not had any 16e V5 task so can't comment on that one.

That screenshot shows points. It's not a lot, sure, but the project itself isn't going to issue large points like the PG CUL tasks. As leadeater said, you NEED to run the BOINC built-in benchmark because the project uses CreditScrew, I mean CreditNew to calculate points and that's based off the results of the benchmark on your host.

boinccmd --run_banchmarks
boinccmd --host ip:port --passwd password --run_benchmarks
 
Make sure nothing is running on the CPU when you do this (or as little as possible).
 
Project doesn't need to be attached to run the benchmark. 
After the benchmark, next time the host communicates with the project it will update the benchmark.
Tasks downloaded BEFORE the benchmark will not be updated. So benchmark FIRST before downloading tasks.

Going via the Pentathlon chat you need to run the BOINC benchmark first before requesting any work, after attaching to the project possibly.

Marathon project has been announced. It is Primegrid's Cullen subproject. For those not familiar, it is similar to running Prime95 large FFT so prepare yourself!
 
Rough optimisation guide:
The tasks currently use about 21MB of data (see edit at bottom for updates) and generally run fastest if you run multiple tasks in total not exceeding the L3 cache size of your CPU. If one task exceeds the L3 cache of your CPU, run 1 task. The number of threads per task can be controlled in Primegrid settings. If you have multiple different systems, you can use more than one venue. Generally speaking run it only on real cores so don't fill up all threads.
 
e.g. on my 7800X3D with 96MB of L3 cache, in theory I should run 4 units at the same time for maximum performance.
 
This can be checked by running a benchmark in Prime95
 

Try using the settings above as a starting point. 2688 is the current largest FFT size used by the project. This may go up during the challenge! Note the software can use different optimal FFT sizes depending on CPU architecture. If you get no result, try lowering the minimum size a bit to find the nearest lower FFT size.
Tick the 2nd check box, as the project uses LLR. It doesn't seem to make much difference so probably doesn't matter if you forget.
Uncheck "Benchmark Hyperthreading" as generally it doesn't help but still increases power consumption on Intel CPUs. You can try it anyway if you want to see what happens.
"Number of workers" is the number of tasks to try at the same time. On my system it defaulted to 1, 2, 8. You can edit it for other divisions of your core count. I added 4 here, as that is interesting.
You can reduce the time to run at the bottom to the minimum 5 seconds to make it a bit faster.
 
You should see output something like the above. Basically you want the biggest number after throughput. As theory predicted, 4 tasks (4 workers) at the same time gave the highest throughput, but note it isn't that much faster than one task using all the cores, about 4%. You may chose slightly lower throughput if you want shorter individual task runtimes, which could be handy at the end if you want to squeeze out a unit before the deadline.
 
Note benchmark numbers can't be directly compared at different FFT sizes! They get lower as FFT size gets bigger.
 
Special considerations:
For CPUs with split L3 caches (Zen 2 and earlier with 6 or more cores, Zen 3 and newer with 12 or more cores) you want to consider each CCX as its own CPU initially. Generally you'll probably run 1 task per CCX if the cache is big enough. If not, one task per whole CPU. 3rd party software like Process Lasso can help prevent Windows messing up scheduling but I can't advise the exact settings required. Similar to above applies if you have NUMA or multi-socket systems. Because the software doesn't generally benefit from HT/SMT, if you have it enabled on your system you should set the BOINC client to use the % of cores vs threads. e.g. if you have a 8 core 16 thread system, set BOINC client to use 50% of CPU cores. Alternatively you can turn off HT/SMT and run 100%. I don't have experience with hybrid Intel CPUs. You'll have to test if using E cores helps or hinders. I'd guess only using P cores is probably optimal. If you have Intel mesh cache CPUs (e.g. Skylake-X, Cascade Lake-X and similar Xeons) count L2 + L3 instead of L3 alone. These are heavily weighted to L2 and it does help. On most other CPUs L2 is insignificant. If you don't have enough cache for 1 task, it will use ram and therefore ram performance will impact overall performance. Bandwidth generally helps more than timings.  
Edit: as expected the FFT size is increasing over time.
Max FFT size and associated data size per work unit:
2 May AM 2688k - 21MB
4 May PM 2880k - 22.5MB

cli users beware, don't accidentally run `boinc` in a directory that has a dir named `projects`. IT WILL DELETE ALL FILES IN THAT DIRECTORY WITHOUT WARNING!

Spectrum referred me to this thread - I have an AMD Epyc 7551 that I'd be happy to donate to someone that will use it purely for folding. I just can't afford the power (and motherboard) costs to fold myself currently but still want to help however I can. You can message me here or on discord (same name, SwiftDW)

Sorry I'm late guys, but I finally built my new PC with my 408-
I missed it!?!?!?!?! FUUUUUUUUUCK
Well at least I can still comment about the eve-

This points to a marginal solder joint that has a micro fracture - it works when warm and then when it cools down it will disconnect again.

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2

Well, it happened. We are officially no.2