- Joined
- Aug 13, 2001
- Location
- Boston, MA
Recently upgraded my cpu and am looking for intense burning programs for my entire system. Thought I'd see what you guys use.
All avaliable via freshmeat:
stress: Does mem alloc at any given size and number of threads. Also does I/O and HDD. Simple application seems very good. Oh yeah, also does cpu but i don't use this proggie for cpu. overall, very good, I use it for hdd, io, and mem.
cpuburn: a theoritical program, it is the best to test your cpu. It simply fills all cpu cache with work, which will work the cpu more than any possible program(s) can.
dnetc: Distributed.net client, i use it for rc5, not for burning really but it's on 24/7 to eat up spare cpu cycles.
Of course, remember to always run 1 test at a time. For example, running stress for mem and cpuburn for cpu at the same time is silly because resources are shared and the kernel prempts the processes.
I've tried a few more but these are the ones I now use. Any other O/C proggies comments can go here. (lm_sensors, nv_clock, etc, if you have questions/comments, feel free)
All avaliable via freshmeat:
stress: Does mem alloc at any given size and number of threads. Also does I/O and HDD. Simple application seems very good. Oh yeah, also does cpu but i don't use this proggie for cpu. overall, very good, I use it for hdd, io, and mem.
cpuburn: a theoritical program, it is the best to test your cpu. It simply fills all cpu cache with work, which will work the cpu more than any possible program(s) can.
dnetc: Distributed.net client, i use it for rc5, not for burning really but it's on 24/7 to eat up spare cpu cycles.
Of course, remember to always run 1 test at a time. For example, running stress for mem and cpuburn for cpu at the same time is silly because resources are shared and the kernel prempts the processes.
I've tried a few more but these are the ones I now use. Any other O/C proggies comments can go here. (lm_sensors, nv_clock, etc, if you have questions/comments, feel free)