|
Performance at various tasks can be very different. Generally per clock per core C2D is slightly better than Athlon II. i3 tends to be a bit faster than C2D, but I doubt it will do a noticeably better job a rendering heavy subs.
Intels naming scheme sucks. Some i5's indeed do not support turbo. The Xeon naming scheme was okay, but now it's this e3/5/7 bs just like the desktop/mobile. Hopefully Opty's won't suffer from poor naming, but AMD just did an Intel naming scheme for their desktop/mobile as well.
C2D is not related to i3 much. It's a huge uarch change going from Core2 to Nehalem. I would not base Nehalem/Westmere/SB/IB performance estimate in a specific task from Core2 performance in the same task.
btw, we have so many issues with vsfilter it seems...
|