Stereodude
2nd January 2003, 16:13
I've been having issues with CCE. I have a P4 2.4b. I also have some watercooling on it and the urge to overclock. I am currently running 3.06gHz (170Mhz FSB with DDR memory at 340Mhz). The machine is stable (passes prime95 and every other test). I'm running Win XP Pro the latest build of CCE 2.66.0.7.
Here's what I posted in another thread ( http://forum.doom9.org/showthread.php?s=&threadid=41570 ) since it outlines very specifically the issue that CCE has.I put a partition on the very front of my WD2000JB. I put the AVI file (HuffYUV compressed) that I'm encoding in this partition and it is the only file in that partition so there is no fragmentation. The drive can sustain 56.5MBytes/sec reading this file. That is at least 5x what's needed to play it real time. I can encode it to the tune about 1.05x or so. CPU usage averages about 82%. If I put the file on the end of a slower HD (WD800JB) where sustained performance is lower (29.2Mbyte/sec) it encodes slower (about .9x) and the CPU usage is proportionately lower.
I've been using the performance monitor in XP to watch disk utilization and other performance variables. Neither of the two drives are really being stressed. They still have over 75% idle time.
Now to eliminate HuffYUV as the problem I output a uncompressed 24 bit AVI at the same resolution (720x480) to the WD2000JB and the performance is abysmal at .25x or so. The HD is fast enough to easily play the file in real time, but still the lack of compression was very detrimental to CCE's speed.
I performed another test. My machine has 1 gig of RAM in it. I trimmed down my test file to about 500 meg (so the entire file could/would be cached). CCE then tears through file using 100% CPU the entire time it reports speed above 1.2x. It's still climbing at the end of the clip.
I've also done some testing at 2.4gHz. The same effect is noticable if the source file is fragmented or on a slow drive. If the file is unfragmented and on the front of a fast drive at 2.4gHz it will sustain 100% CPU usage. However, at 2.4gHz if the file to be compressed falls at the end of a drive (slowest part of the drive) or has fragmention occuring in it CCE will not be able to sustain 100% CPU usage either.
I've ruled out memory BW as the source of the problem. The Asus P4PE board I'm using allows the memory multiplier to be adjusted. Running 2.4gHz with a 266MHz memory bus and 2.4gHz with a 355MHz memory bus yeilded the same results. My memory is running at 2-2-2-2-6 BTW (very agressive timings) in all tests.
CCE seems to be fairly poorly written for how much it costs.
Stereodude
Here's what I posted in another thread ( http://forum.doom9.org/showthread.php?s=&threadid=41570 ) since it outlines very specifically the issue that CCE has.I put a partition on the very front of my WD2000JB. I put the AVI file (HuffYUV compressed) that I'm encoding in this partition and it is the only file in that partition so there is no fragmentation. The drive can sustain 56.5MBytes/sec reading this file. That is at least 5x what's needed to play it real time. I can encode it to the tune about 1.05x or so. CPU usage averages about 82%. If I put the file on the end of a slower HD (WD800JB) where sustained performance is lower (29.2Mbyte/sec) it encodes slower (about .9x) and the CPU usage is proportionately lower.
I've been using the performance monitor in XP to watch disk utilization and other performance variables. Neither of the two drives are really being stressed. They still have over 75% idle time.
Now to eliminate HuffYUV as the problem I output a uncompressed 24 bit AVI at the same resolution (720x480) to the WD2000JB and the performance is abysmal at .25x or so. The HD is fast enough to easily play the file in real time, but still the lack of compression was very detrimental to CCE's speed.
I performed another test. My machine has 1 gig of RAM in it. I trimmed down my test file to about 500 meg (so the entire file could/would be cached). CCE then tears through file using 100% CPU the entire time it reports speed above 1.2x. It's still climbing at the end of the clip.
I've also done some testing at 2.4gHz. The same effect is noticable if the source file is fragmented or on a slow drive. If the file is unfragmented and on the front of a fast drive at 2.4gHz it will sustain 100% CPU usage. However, at 2.4gHz if the file to be compressed falls at the end of a drive (slowest part of the drive) or has fragmention occuring in it CCE will not be able to sustain 100% CPU usage either.
I've ruled out memory BW as the source of the problem. The Asus P4PE board I'm using allows the memory multiplier to be adjusted. Running 2.4gHz with a 266MHz memory bus and 2.4gHz with a 355MHz memory bus yeilded the same results. My memory is running at 2-2-2-2-6 BTW (very agressive timings) in all tests.
CCE seems to be fairly poorly written for how much it costs.
Stereodude