Points & Floating Point Operations
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 70
- Joined: Sun Apr 05, 2020 12:36 pm
- Hardware configuration: 2 iMacs and 1 dedicated Windows 10 Pro rig with 1 RTX 2070 Super and 1 RTX 2060 KO
- Location: Burlington, Ontario. Canada
Points & Floating Point Operations
I understand from Folding@home that WU's are benchmarked to determine their points value and I also see many comments referring to points as a measure of science performed. My question: Can points be correlated with floating point operations performed?
-
- Posts: 1996
- Joined: Sun Mar 22, 2020 5:52 pm
- Hardware configuration: 1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21 - Location: UK
Re: Points & Floating Point Operations
Yes and no (probably more no than yes tbh - edited) ... in base points there will be a fairly close correlation (loosely so not direct - edited) subject to vagaries of benchmarking and project methodology ... but the QRB processes wraps this by introducing a time based element to point allocation ... there is an FAQ on the main FaH website that explains in some detail how the points are calculated iirc
Last edited by Neil-B on Tue Jun 30, 2020 1:23 pm, edited 2 times in total.
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070
(Green/Bold = Active)
Re: Points & Floating Point Operations
Be careful. Though you didn't say it, you may be assuming something incorrect about GPU performance numbers.
Floating point operations performed cannot be correlated with the GPU's advertised theoretical GFLOPS performance numbers. If a GPU has, say 5000 shaders, it takes the same amount of time to perform 5000 Floating Point Operations as it does to perform 1 FLOP.
A GPU with 2500 shaders running at twice the clock rate will have the same GFLOPS number but will perform quite differently.
Floating point operations performed cannot be correlated with the GPU's advertised theoretical GFLOPS performance numbers. If a GPU has, say 5000 shaders, it takes the same amount of time to perform 5000 Floating Point Operations as it does to perform 1 FLOP.
A GPU with 2500 shaders running at twice the clock rate will have the same GFLOPS number but will perform quite differently.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.