...
Using mprime
I only use option 15 16 (Options/Torture Test) since we just need mprime for stress testing. It will max the detected threads across all CPU's, I just hit 'enter' when it asks 'Number of torture test threads to run (x):'.
Code Block | ||
---|---|---|
| ||
## Assuming you're not already in the mprime directory you created if you're doing this all in one go from this article cd mprime ./mprime ## If this is your first time extracting/using, it will ask if you want to join GIMPS- I usually hit 'n' since this is for troubleshooting only anyways [root@c103454 mprime]# ./mprime Main Menu 1. Test/Primenet 2. Test/Worker threads 3. Test/Status 4. Test/Continue 5. Test/Exit 6. Advanced/Test 7. Advanced/Time 8. Advanced/P-1 9. Advanced/ECM 10. Advanced/Manual Communication 11. Advanced/Unreserve Exponent 12. Advanced/Quit Gimps 13. Options/CPU 14. Options/Resource Limits 15. Options/Preferences 16. Options/Torture Test 17. Options/Benchmark 18. Help/About 19. Help/About PrimeNet Server Your choice: Number of torture test threads to run (80): Choose a type of torture test to run. 1 = Smallest FFTs (tests L1/L2 caches, high power/heat/CPU stress). 2 = Small FFTs (tests L1/L2/L3 caches, maximum power/heat/CPU stress). 3 = Large FFTs (stresses memory controller and RAM). 4 = Blend (tests all of the above). Blend is the default. NOTE: if you fail the blend test but pass the smaller FFT tests then your problem is likely bad memory or bad memory controller. Type of torture test to run (4): |
Usually run test (2) for CPU only, (3) for Memory only, and blend Blend (4) to perform both.
Code Block | ||
---|---|---|
| ||
Your choice: 16 Number of torture test threads to run (80): Choose a type of torture test to run. 1 = Smallest FFTs (tests L1/L2 caches, high power/heat/CPU stress). 2 = Small FFTs (tests L1/L2/L3 caches, maximum power/heat/CPU stress). 3 = Large FFTs (stresses memory controller and RAM). 4 = Blend (tests all of the above). Blend is the default. NOTE: if you fail the blend test but pass the smaller FFT tests then your problem is likely bad memory or bad memory controller. Type of torture test to run (4): Customize settings (N): y Min FFT size (in K) (4): Max FFT size (in K) (8192): Memory to use (in MB, 0 = in-place FFTs) (382415): 360000 Time to run each FFT size (in minutes) (6): Run a weaker torture test (not recommended) (N): Accept the answers above? (Y): |
...