![]() Current hardware is designed to work couple of hours per day under low or mixed load. Regardless of used CPU stress software it may damage something when it's running at 100% load for many hours. We are using desktop hardware and barely anyone is using it for real work but most users care about it like it was mission critical hardware performing 24h+ stability tests. DDR5 RAM & PCIe4.0 SSDPre-installed 32G(2x16G) DDR5 RAM up to 4800MHz. GTR6 is the highest configuration of AMD products in the Mini PC category. Other thing is that long stability testing. Ryzen9 6900HX ProcessorBeelink GTR6 comes with AMD Ryzen9 6900HX Processor, 8-Core 16-Thread up to 4.90GHz. So you spend 1h on CPU + 1h on memory/cache and it's done, instead of 2 days of tests which are not showing any special differences. Noone is saying to run 24h+ in new Prime95 but 30-40mins usually stress CPU more and finds any errors faster than 24h of lighter stability tests. So you are testing stability but you won't check if it's stable when full CPU functionality is utilized ? Later you see guys who are complaining that after 5h Prime or anything else it's still crashing in some games. It's stressing CPU more for sure but if your daily applications are using these instructions then you won't turn it off. Heres my specs/build Case: Lian Li LI PC-O11 Dynamic EVO Motherboard: ASUS ROG Maximus Z790 Extreme CPU: Intel 13900K CPU Cooler: EVGA CLCx 360mm All-In-One LCD CPU Liquid Cooler (swapped out EVGA fans for phanteks & set to exhaust position) Thermal Paste: Removed EVGAs stock paste. I also still have no idea why suddenly all are afraid to use new Prime95 or other programs which are using new instructions. Every test is good for some purposes so for overall stability you have to use couple of programs. Last edited by mr clark25 December 27th, 2009 at 01:00 AM.If it's not fully stressing CPU then it's not testing it right.ĭuring stability tests you have to check various scenarios like constant full load but also mixed load as sometimes when CPU load drops to ~0-10% then C stages or other settings are causing voltage etc drop and when it jumps quicky to full load then not everything will react on time ( that's why some boards have manual vrm frequency and other things ). if i could compare two commands (while running the "watch" command), i could really do something with this. (the "test" part of "stress test")ģ.i cant do this by myself. (the "stress" part of "stress test")Ģ.i need a way to compare the output of two commands. this works great for stress testing, but i can only test my cpu for heat output. i did some experimenting, and came to what i have now.ġ. i knew then that i had found an use for this. i had the system monitor open on accident when i typed "pi 500000" into a terminal. I knew there had to be some use for this. i also figured out that it is much faster than super pi, so the results weren't comparable. i posted to the forums about this and found out about the "time" command. so, i then typed this into the terminal: pi 1048576 and timed it myself. then i went to the forums to try to find out how many digits super pi calculated pi to. Why not boot into a live Linux ISO and then run mprime or stress (Two different programs, the former allowing for more benchmarks and stress-tests. i quickly found out that i can chose how many digits to calculate pi to by typing a number after i type pi. it said that i needed a program to do that. so, i started trying to find an alternative. but, i kept getting an error, no matter what i did. I was trying to get super pi to work on a computer to see how it compares to other computers. So, for now, i need to know if there is a command (or a way to) that compares the output of two commands, and alert me if the two outputs are different. i have a processor with 2 threads, and, if i run this in 4 terminals at once, it works just as good as prime95. You may need to increase the number after "pi" if you have a faster cpu. (one for each thread your cpu has) i recommend that you run two for each thread because cpu usage will drop to about 90% every so often if you don't. The only catch is that you must run this command several times, all in separate terminals, all at the same time. (command: sudo apt-get install pi)Īnd this command works great for stressing a cpu: watch -n.1 pi 2000000 This is a summary of what i have come up with so far: ![]() (like stop or bring up a warning) i also need it to work with the "watch" command. To start, i want to know if there is a way to compare the output of 2 commands, and do something if the two outputs are different.
0 Comments
Leave a Reply. |