QUOTE(timljh @ Dec 30 2007, 02:07 PM)
for consumer like us maybe not really realise wat native quad can do, i juz finish my research on multicore for my assignment, licensing will be a prob for MCM processor like core 2 quad, the charge for software is double as many company accept a MCM processor as 2 processor instead of 1 for native quad, therefore licensing cost for business is considerably high. the performance for native quad will outperform non-native in a multiprocessor system.
Added on December 30, 2007, 2:12 pmthats same goes to intel as it wont go to native till tat period.
I have to disagree. Consumers nowadays are doing the following things:
1. Video encoding - transcoding IPOD Video/Touch/iPhone, transcoding TVB dramas, PC to XBOX360 etc
2. Picture processing - there is a growing consumer base going forward to SLR photography, processing RAW using Adobe Photoshop and other consumer retail software
3. Home Video encoding - encoding/decoding recorded home video to DVD
4. New generation PC gaming - Crysis, etc
These are the applications that are multi-threaded SMP in nature. According to Techspot review of an Intel Q6600 G0 (http://www.techspot.com/review/36-intel-core2-quad-q6600/page6.html), on real world content creation applications, it has an average of 10-30% improvement (time savings and performance) over X6800. Thats close to 80% time improvement over any single core processors. So the only thing a consumer will not go for quad core is actually the price and not whether they can fully utilize a quad core processor. Dual cores are cheap as chips nowadays so again thats another sweet area to rake profits. Just look at the E-series and upcoming Celerons.
On other applications, you're right because current retail software are way behind in terms of SMP and will only be good on enterprise applications. But that trend will change very soon since Windows Vista is a platform for multi-core processing already. We can expect situation to improve. Right now buying a Quad Core is rather to secure the future. Its nice to know that there are more headrooms to discover when more software introduce SMP.
Now with regards to licensing, the licensing charges are per physical processors and not virtual processors like P4 HyperThreading and in this case of interest multi-core processors but with an exception (depending on individual policies); that per physical processor does not have more than 4 processing cores. That is one reason the industry is pushing multi-core products because you'll save a lot of value when it comes to this. Check out the following references:
http://www.vmware.com/download/eula/multicore.htmlhttp://www.microsoft.com/licensing/highlights/multicore.mspxI'm sure there are more software companies implementing the same licensing policy especially when Microsoft adopts this policy. I just hope you didn't fail your assignment and have included reasonable considerations for this point.
Now who say native quad-core processors will beat non-native quad-core processors? During the 2006, there has been numerous discussions that non-native multi core processors will have to depend on FSB to transfer information to each processor core. That was the Pentium D. Today, non-native quad-core is as good as native quad core. Ever heard of shared L2-cache? Thats how Core/Core2 processor architecture share information which releases a lot of overhead. The only exception is when 1 core of silicon A wants to share information with another core on silicon B on a quad core processor where it had to go through FSB.
Intel will not go native quad core is because the benefits are low at this point and the risks are very high. Yield problems is going to create havocs. One faulty core will jeopardize the whole 4 core silicon. Thats 100% lost per processor. A native quad core silicon die takes up a lot of space, thats up to 2 times any dual core silicons per silicon wafer. Imagine the loses at this point. AMD had to implement e-fuses for its faulty Phenom and introduce tri-core processors later in the future. Look at Sony's Cell processor development. It'll tell you a lot going that path of road.
By going non-native, Intel can maximize its yield and can make decision very late into the production stage whether to make a Core 2 Duo or a Core 2 Quad. That gives Intel a lot of flexibility in determining how many C2D or C2Q depending on their marketing strategy.
This post has been edited by davidmak: Jan 11 2008, 05:24 PM