On Sep 22, 9:35 am, nickolas...@gmail.com wrote: > > md5 -t is quite a small benchmark, even with his misfunctioning CPU it > > took <6 seconds to complete. > > > If his problem is a misapplied heatsink/fan, then his CPU could be > > throttling when it gets hot, the hotter it gets the more it throttles, > > which could explain his massive buildworld walltime. Perhaps running > > something like: > > > apply -0 "md5 -t" `jot 10` > > > would display a notable difference. >
I don't think is heat & throttling related. Here's the temps while doing a make -j16 buildworld: dev.cpu.0.temperature: 57.0C dev.cpu.1.temperature: 57.0C dev.cpu.2.temperature: 54.0C dev.cpu.3.temperature: 54.0C dev.cpu.4.temperature: 57.0C dev.cpu.5.temperature: 57.0C dev.cpu.6.temperature: 55.0C dev.cpu.7.temperature: 55.0C IMO, the problem is preventing the system from even loading up the CPU's enough to even get hot - I have never seen it over 61 C. If sit & watch top -P during a buildworld, it rarely get's all 8 CPU's loaded up with idle numbers near 0%. A vast majority of the time one CPU is maxed and the others are mostly idle. > You may also run openssl speed or "linpack" test > (/usr/ports/math/linpack) or hpl (/usr/ports/benchmarks/hpl) to load > your CPU > _______________________________________________ > freebsd-sta...@freebsd.org mailing > listhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
