olympia Wrote:I really think you should be more careful about that. Your voice is loud and people are hearing that. Read back just two pages. Alanwww1 also stated, that on Hardy, he was able to see smooth playback of killa even with an E7200 at stock speed. I have the same experience with E7300 and E8400, so forget about cache size.
I just wanted to raise a possible chance why you experienced slow playback at 2.66, not to begin an argue with you........
Well there's this. I'm not exactly seeing bunches of people stepping forward and saying 2.66ghz is enough and I don't see it myself.
My test 12/20 with it dropping frames at 2.7ghz and at 2.6ghz both of those on Intrepid. 3ghz cleared the drops. Here's where you popped up stating that it wasn't dropping frames for you on an 8200. So which CPU are you running an E8200 or E7300 along with an E8400? Have you tried underclocking the E8400? alanwww1 says he can run 2.66ghz in Hardy but 3ghz drops frames in Intrepid?
Why did I conclude cache? Because a dual core Celeron clocked to 3ghz dropped massive frames - on Intrepid. I'm open to alternative explanations, in fact I'd like to hear them. I can also state that compile times were noticeably slower vs my Hardy based 3ghz (overclocked) 65nm machine.
I will ask again - aside from the two of you - who is able to play the Killa' file at less than 3ghz and what is the config capable of doing this? How can we narrow down the performance difference?
My goal is simple - people are asking what hardware to buy and I'd like to be able to answer the question with something concrete and repeatable. I have tested on my own, documented the results, and concluded that a 3ghz C2D is needed or at least was less than a month ago. If you guys have found otherwise than others, including myself, ought to be able to repeat the performance and we can lower the requirements bar. Bueller?
Meanwhile you 2 guys are having issues on Intrepid that I am *not* seeing and are dropping frames. Is this issue appearing on the same machines that played fine under Hardy? I will ask again, anyone else on Intrepid *not* seeing this issue? Let's try to find what is common in the machines that ARE working. Tonight I didn't get to dork with my working box - I was building an ATOM based desktop
but I am open to pulling config files and running commands to probe the config as well as noting patches it may or may not have if folks can tell me what they want to see. Oh and I will try dropping to 2.66ghz too if folks want but I am pretty sure I know what will occur <shrug>
