I don't believe that CPU % is a good guage of efficient rendering/encoding. Maybe with WMV but definitely not MPEG. The ultimate test is how long did the render take to completion? If you missed my previous posts, there is a problem with Vegas rendering to MPG with Dynamic RAM setting >0 and < 128:
The 750 setting rapidly ran the page file up to 1GB under task monitor, resulting in a lot of CPU bouncing between 0% and 90% as you reported. But it very shortly stabilized to 88%-96%. Both of the other RAM settings also performed in that range. Again, this was with MPG output.
Several people have reported render time improvements when they switch from 16MB and 64MB to 0 or > 128.
I have been testing on WMVHD and M2T files because I am a HD guy. But I did notice that a 5 minute WMV rendered faster than a MPG with these settings I didn't realize that the type of file made a difference.
To Vegas developers
Is there away that Vegas 6 could do a render analysis vefore it starts chugging to automaticly figure out the settings for the fastest render bassed on the amount of ram present, the type of plug and the amount of available cpu or threads?
Some of this info could be asked when installing Vegas on the PC