#GOOD CPU STRESS TEST SOFTWARE#Since most users test their rigs without a sense of scale for power and temperature, they can't compare apples to apples, especially when combined with major variables such as differences in ambient temperature, hardware configurations and software utilities. #GOOD CPU STRESS TEST CODE#The corresponding machine code (42 bytes): 00000000 48 31 ff 48 8b 4c 24 10 48 8b 09 80 e9 30 7c 11 |H1.H.L$.H.0|.|Ġ0000010 48 6b ff 0a 48 0f be d1 48 01 d7 48 c1 c9 08 eb |Hk.H.H.H.|Ġ0000020 ea b8 25 00 00 00 0f 05 eb fe |.%.As the author of the Intel Temperature Guide - I can fully appreciate how much work went into creating this outstanding article, which has been sorely needed! In theory it would be necessary to add a global _start followed by a _start: label at the beginning, but ld manages to fix it by itself with little fuss. You can assemble it with nasm -f elf64 -o stress.o stress.asm & ld -o stress stress.o The NASM minified source (146 bytes): xor rdi,rdiĪccepts a parameter on the command line specifying the number of seconds to run in the range (0, 9999999] can be interrupted with the usual Ctrl-C. X86_64 assembly on Linux - 146 (source), 42 (assembled code) Set_time_limit($_REQUEST) while(!0) Īs i told, I'm not targeting the console solution, but they have to get the credit for this one.Īnother answer could be this "monster", which is just both answers combined: to the end of the url or submit a post (using a form or even ajax). This is done by building an asm file with a minimal Elf header of its own, and skipping the use of ld altogether.īuilt with nasm -f bin tiny_cpu_stresser_elf32.asm -o tiny_cpu_stresser_elf32 This will execute without any additional support on any linux based platform, or potentially even without an operating system. I bet this is the smallest correctly formed Elf format binary that can be made to perform this function. After all, this should be fun – not work. I'm definitely not expecting you to produce a multi-core solution. Since the question came up in the comment area… you only need to target 1 CPU core. The winner is the one presenting the most minimal (in size) sourcecode that complies to the above “must” and “must not” conditions. Present the smallest sourcecode possible. #GOOD CPU STRESS TEST VERIFICATION#(as long as it allows practical verification of its functionality by running it) may use any programming or scripting language.may use any approach/algorithm/functionality to produce expected 100% CPU load.(Proposing shortcuts in the likes of system('cpuStressThing.exe') disqualifies your proposal.) must not use 3rd-party programs or tools which replace expected functionality.(Even a hamster could stress a Comodore64… therefore, you must target a current operating system.) #GOOD CPU STRESS TEST MAC#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |