If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
New! You can now log in to the forums with your chaos.com account as well as your forum account.
in the video he said: 4 processors 6 cores each? and then he reffers to it as a 6 core cpu! so which one is it??? I actually watched the video twice to confirm...
so confused now
From what I understand concerning heat and the i7s, Intel has put some fail-safes in place to ensure that the processors will first downthrottle and eventually just hard shutdown when approaching critical temps to avoid system damage. What appears as TJunction max in programs like coretemp and realtemp is the threshold for automatic shutdown. This value is labeled as "TJunction Target" for the core i7 and is currently understood to be 100C. Within 10C below that is where the processor takes control of it's multiplier and downthrottles to keep itself from reaching the TJunction max. In the event that your temps are throttling because of a bad HS seating or voltage issues, you could possibly reach TJunction max, resulting in a shutdown, but this is very very unlikely because the system will become unstable and probably crash before even hitting this threshold. Just stay away from 90C so that you don't have to test these out
From my time spent reading about and fooling with the i7 on air cooling, I personally feel that 85C as reported by a calibrated realtemp is a safe barrier when testing OC settings using small FFT stress test in Prime95, and 75C for small FFT stress temps is a good barrier for 24/7 usage. Right around 68C is Intel's stock i7 temps...but if you are really concerned with operating at Intel's default specifications then you probably shouldn't be overclocking the processor at all.
hi guys
if you like, head over to my benchmarking site, you'll be able to setup a workstation profile and then easily add your render times to the database and compare to others. i've been seeing some smoking times from i7 machines. it would be nice to get more benchmarks for the vray scenes http://www.3dspeedmachine.com/?page=3
OS: xp64
Software: 3ds max 2009 - 64bit
Renderer: VRay 1.50 SP2
HW:7 pc DualXeon quadcore
RENDERTIME: 0h 03m 10s
RENDERTIME for 3000*2063: 0h 33m 13s
Try to the same resolution (3000*2063), just for fun. After try 7000 px. What's you TOTAL Ghz?
first beta quick and dirty was 9min41s in 3500px with 50 times 20ghz (400cores)
the total Ghz is not that accurate - loading scene + preparing nodes cause wast in time
I am not useing the Vray distributed render - I have my own solution which need to be more optimised
the same in 7k px was about 19min
all the farm eating the image the same time should be less 6 / 10 min
__________________________________
- moste powerfull Render farm in world -
RebusFarm --> 1450 nodes ! --> 2.900 CPU !! --> 20.000 cores !!!
just 2,9 to 1.2 cent per GHZ hour --> www.rebusfarm.net
Comment