Alex Thames
June 26th, 2007, 01:02 AM
I recently just put together a brand new desktop computer.
Specs:
CASE: Antec 900
MOTHERBOARD: Gigabyte GA-P35C-DS3R LGA 775 Intel P35 ATX Intel Motherboard (P35 mobo)
CPU: Intel Core 2 Duo Allendale E4300 1.8ghz 800mhz FSB 2mb L2 shared cache
MEMORY: Crucial Ballistix 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel Kit Desktop Memory
GRAPHICS CARD: MSI Nvidia 8600 GTS (heatsink version)
AUDIO CARD: none (onboard sound)
POWER SUPPLY UNIT: Antec Earthwatts 500W
HARD DRIVE x1: Seagate Barracuda 7200.10 ST3500630AS 500GB 7200 RPM SATA 3.0Gb/s
FIREWIRE PCI CARD: SYBA IEEE 1394a FireWire PCI Card with Internal 9-pin Header Model SD-VIA-FW1E1H
AFTERMARKET COOLING: Scythe Ninja Plus B SCNJ-1100P 120mm Sleeve CPU Cooler (took out stock Scythe fan and replaced with Noctua NF-S12-800 120mm fan)
DVD BURNER: Lite-on 20x Lightscribe SATA DVD Burner
The Antec TriCool 120mm fans are all set on low, and the Antec 200mm fan is also set on low, while the Noctua fan is set at 12V at its fastest speed (800 RPM for the slow version).
So, I did my rendering to see how fast my computer could render in Vegas 7.0e. I closed all applications and only had background processes running (about 35-40 processes, which use 0% of the CPU processing power if I'm doing nothing and just letting the computer idle). No anti-virus, no firewall, no spyware killers, etc.
I opened up Vegas 7.0e and tried rendering the test render-HDV file someone had created. The fastest time I've seen was with someone's quad core Intel QX6700 2.66mhz, which rendered the file out in 2 minutes 0 seconds. He was able to repeat this a few times I think.
The first time I tried rendering the benchmark file, I ended up with 3 minutes 16 seconds, which I'm quite pleased with considering that I'm using the lowest end Core 2 Duo CPU. It was rendering at 61% of the quad core.
Note: my hard drive is partitioned into two drives. C Drive is 50 gb, D Drive is 415gb. I have around 50gb free total left because I copied a lot of files over from my external drive.
Then I installed antivirus, firewall, spybot, etc. I tried rendering with and without these programs on.
The following are the times I've gotten:
1st Trial: 3:16
(no antivirus, firewall, spyware, etc.) I wasn't paying too much attention, but I think it was at 100% CPU usage for the entire test.
2nd Trial: 3:20
(with antivirus, firewall on...this is acceptable, but I noticed that the CPU usage went down to 99% for a quick moment)
3rd Trial: 3:40
(with antivirus, firewall on...this was much longer than expected, and I suspected that CPU usage went down considerably)
4th Trial: 3:40 again
(with antivirus, firewall on...this time I watched the CPU usage and I noticed it would drop to around 50%, sometimes 60% and 70%ish for several seconds, then jump back up to 100%, then after awhile, go back down to the high 90s, then 100, then 50ish, etc.)
5th Trial: 3:18
(with antivirus, firewall on...this was a nice time, though not as fast as my 1st trial. I noticed the CPU usage was not at 100% all the time, but when it did drop, it was only for a few, not several, seconds and they only dropped to the mid to high 90s, never to the 50% level)
6th Trial: 3:39
(with antivirus, firewall on...again, horrible performance with the CPU dropping to the 50s a lot)
7th Trial: 3:39
(same thing as 6th Trial)
8th Trial: 3:39
(again...)
One thing I noticed on the 8th trial that I wasn't paying attention to on the previous trials was the graphic chart of the CPU usage history showed the two cores...the core on the left was displaying much lower CPU usage than the right core when there was a drop. For example, if the CPU usage dropped to 50%, the left core would show that it's usage was much lower than the right core.
Here is a screenshot of what I mean: http://img256.imageshack.us/my.php?image=sonyvegashdvrendertestgb9.jpg
It shows the 50% level and that the left core drops more than the right core.
I'm not sure why? Anyone have ideas? My hypothesis, from what I've read online, is that the Scythe Ninja heatsink fan is so heavy and since my motherboard is mounted vertically, the heatsink base is not coming into full contact with the CPU cores. I did apply thermal paste. So, I think gravity is pulling the heatsink fan down a bit resulting in better contact with the bottom (right) core than the top (left) core. That means the top (left) core is not getting cooled as much as the bottom (right) core, which may or may not explain the difference in core usage.
Would different cooling performance on the two cores affect render speeds? Would the CPU temperature in general affect rendering speeds if it is able to run stably? Note that I did not overclock anything. No CPU, no memory, no mobo, no graphics card OCing.
But my MAIN question is, why does the CPU usage drop to the 50% level (or even the 60-70-80% levels) at all? It slows down render speed considerably, and Vegas being able to use multiple cores should be using the CPU at 100%. 93% and up for a few seconds might be acceptable, but when it drops to the 50% level for up to 10 seconds, it really kills the render time.
From the trials, you can see that difference from the fastest time (3:16) and the slowest time (3:40) is huge percentage wise. I can only imagine how much longer it will take rendering out my big projects, 2-3 hours of HDV 1440x1080 if the CPU usage drops to 50% this much.
Out of eight trials, only 3 times was the CPU able to reach optimal/near optimal peaks (mid 90-100%). This seems to suggest that more times than not, the CPU will drop to 50%, and more times than not, I will get a slower
render time.
How can I fix this? And why does it do this?
Thanks!
EDIT: Just did a 9th Trial: 3:41, the slowest time yet. It lingered in the 50% level several times, lasting anywhere from a few seconds to 11 seconds. I'd estimate the time it spent at the 50% level to be for about 30 seconds total during the entire 3 min 41 seconds.
And a 10th Trial: 3:41 again, the slowest. It dipped into the 50s four times, each time lasting around 10 seconds for a total of 40 seconds (estimate).
I don't know what to do to get it back to 100% consistently.
Specs:
CASE: Antec 900
MOTHERBOARD: Gigabyte GA-P35C-DS3R LGA 775 Intel P35 ATX Intel Motherboard (P35 mobo)
CPU: Intel Core 2 Duo Allendale E4300 1.8ghz 800mhz FSB 2mb L2 shared cache
MEMORY: Crucial Ballistix 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel Kit Desktop Memory
GRAPHICS CARD: MSI Nvidia 8600 GTS (heatsink version)
AUDIO CARD: none (onboard sound)
POWER SUPPLY UNIT: Antec Earthwatts 500W
HARD DRIVE x1: Seagate Barracuda 7200.10 ST3500630AS 500GB 7200 RPM SATA 3.0Gb/s
FIREWIRE PCI CARD: SYBA IEEE 1394a FireWire PCI Card with Internal 9-pin Header Model SD-VIA-FW1E1H
AFTERMARKET COOLING: Scythe Ninja Plus B SCNJ-1100P 120mm Sleeve CPU Cooler (took out stock Scythe fan and replaced with Noctua NF-S12-800 120mm fan)
DVD BURNER: Lite-on 20x Lightscribe SATA DVD Burner
The Antec TriCool 120mm fans are all set on low, and the Antec 200mm fan is also set on low, while the Noctua fan is set at 12V at its fastest speed (800 RPM for the slow version).
So, I did my rendering to see how fast my computer could render in Vegas 7.0e. I closed all applications and only had background processes running (about 35-40 processes, which use 0% of the CPU processing power if I'm doing nothing and just letting the computer idle). No anti-virus, no firewall, no spyware killers, etc.
I opened up Vegas 7.0e and tried rendering the test render-HDV file someone had created. The fastest time I've seen was with someone's quad core Intel QX6700 2.66mhz, which rendered the file out in 2 minutes 0 seconds. He was able to repeat this a few times I think.
The first time I tried rendering the benchmark file, I ended up with 3 minutes 16 seconds, which I'm quite pleased with considering that I'm using the lowest end Core 2 Duo CPU. It was rendering at 61% of the quad core.
Note: my hard drive is partitioned into two drives. C Drive is 50 gb, D Drive is 415gb. I have around 50gb free total left because I copied a lot of files over from my external drive.
Then I installed antivirus, firewall, spybot, etc. I tried rendering with and without these programs on.
The following are the times I've gotten:
1st Trial: 3:16
(no antivirus, firewall, spyware, etc.) I wasn't paying too much attention, but I think it was at 100% CPU usage for the entire test.
2nd Trial: 3:20
(with antivirus, firewall on...this is acceptable, but I noticed that the CPU usage went down to 99% for a quick moment)
3rd Trial: 3:40
(with antivirus, firewall on...this was much longer than expected, and I suspected that CPU usage went down considerably)
4th Trial: 3:40 again
(with antivirus, firewall on...this time I watched the CPU usage and I noticed it would drop to around 50%, sometimes 60% and 70%ish for several seconds, then jump back up to 100%, then after awhile, go back down to the high 90s, then 100, then 50ish, etc.)
5th Trial: 3:18
(with antivirus, firewall on...this was a nice time, though not as fast as my 1st trial. I noticed the CPU usage was not at 100% all the time, but when it did drop, it was only for a few, not several, seconds and they only dropped to the mid to high 90s, never to the 50% level)
6th Trial: 3:39
(with antivirus, firewall on...again, horrible performance with the CPU dropping to the 50s a lot)
7th Trial: 3:39
(same thing as 6th Trial)
8th Trial: 3:39
(again...)
One thing I noticed on the 8th trial that I wasn't paying attention to on the previous trials was the graphic chart of the CPU usage history showed the two cores...the core on the left was displaying much lower CPU usage than the right core when there was a drop. For example, if the CPU usage dropped to 50%, the left core would show that it's usage was much lower than the right core.
Here is a screenshot of what I mean: http://img256.imageshack.us/my.php?image=sonyvegashdvrendertestgb9.jpg
It shows the 50% level and that the left core drops more than the right core.
I'm not sure why? Anyone have ideas? My hypothesis, from what I've read online, is that the Scythe Ninja heatsink fan is so heavy and since my motherboard is mounted vertically, the heatsink base is not coming into full contact with the CPU cores. I did apply thermal paste. So, I think gravity is pulling the heatsink fan down a bit resulting in better contact with the bottom (right) core than the top (left) core. That means the top (left) core is not getting cooled as much as the bottom (right) core, which may or may not explain the difference in core usage.
Would different cooling performance on the two cores affect render speeds? Would the CPU temperature in general affect rendering speeds if it is able to run stably? Note that I did not overclock anything. No CPU, no memory, no mobo, no graphics card OCing.
But my MAIN question is, why does the CPU usage drop to the 50% level (or even the 60-70-80% levels) at all? It slows down render speed considerably, and Vegas being able to use multiple cores should be using the CPU at 100%. 93% and up for a few seconds might be acceptable, but when it drops to the 50% level for up to 10 seconds, it really kills the render time.
From the trials, you can see that difference from the fastest time (3:16) and the slowest time (3:40) is huge percentage wise. I can only imagine how much longer it will take rendering out my big projects, 2-3 hours of HDV 1440x1080 if the CPU usage drops to 50% this much.
Out of eight trials, only 3 times was the CPU able to reach optimal/near optimal peaks (mid 90-100%). This seems to suggest that more times than not, the CPU will drop to 50%, and more times than not, I will get a slower
render time.
How can I fix this? And why does it do this?
Thanks!
EDIT: Just did a 9th Trial: 3:41, the slowest time yet. It lingered in the 50% level several times, lasting anywhere from a few seconds to 11 seconds. I'd estimate the time it spent at the 50% level to be for about 30 seconds total during the entire 3 min 41 seconds.
And a 10th Trial: 3:41 again, the slowest. It dipped into the 50s four times, each time lasting around 10 seconds for a total of 40 seconds (estimate).
I don't know what to do to get it back to 100% consistently.