1 |
On 04/13/2013 01:50 PM, Frank Steinmetzger wrote: |
2 |
> On Sat, Apr 13, 2013 at 07:03:26AM +0200, Tamer Higazi wrote: |
3 |
>> Hi people! |
4 |
>> My old core2duo machine says slowly goodbye and I am at this lever after |
5 |
>> 7 years for buying myself a new developer machine, that should serve me |
6 |
>> well for a long time again. With intel I never had problems, all their |
7 |
>> systems were REALLY stable, and they were really worth their money up to |
8 |
>> the last cent. |
9 |
> |
10 |
> Same situation here -- Core2 Duo T7200 (2 GHz max, but throttled due to |
11 |
> worn-down heatpipe). I'll be buying a new system, too, soon. |
12 |
> |
13 |
> As to the other issues of the thread: |
14 |
> all intel Cores have VT-x (including Core2, by the way), which is basic |
15 |
> virtualisation support. What only a select few have is VT-d, which is I/O |
16 |
> virtualisation. As for the confusion about model range and hyperthreading, |
17 |
> Wikipedia has a very nice comparison chart of all available models: |
18 |
> http://en.wikipedia.org/wiki/Ivy_Bridge_(microarchitecture)#Desktop_processors |
19 |
> |
20 |
> Basically: |
21 |
> i3 = dual-core with HT (2 physical/4 logical cores), no turbo mode |
22 |
> i5 = quad-core without HT (4/4, except one low-TDP model, which is 2/4) |
23 |
> i7 = quad-core with HT (4/8) |
24 |
> |
25 |
> I don't know the technical details very well, but because my Netbook has a |
26 |
> single-core CPU with HT, I read up on it a bit. As I understand it, HT allows |
27 |
> two threads to use the same core simultaneously, if they don't use the same |
28 |
> instruction circuitry. Hence a hyper-threaded single-core is not as fast as |
29 |
> a proper dual-core, because sometimes one thread still has to wait. |
30 |
> |
31 |
>> There are 3 choices: |
32 |
>> |
33 |
>> Intel Xeon E5-2650 |
34 |
>> Core i7 3979 extreme edition |
35 |
>> AMD FX.8350 CPU |
36 |
> |
37 |
> Everything Intel with Extreme in the name is, in my opinion, overpriced for |
38 |
> its bang. If you really need as much bang as possible and afford it (like when |
39 |
> you earn your money with that bang), then why not. |
40 |
> But if you say your Core2 served you well, then you could go a more pragmatic |
41 |
> approach of "3 times more power than before is enough for me" and save a few |
42 |
> 100 bucks, or maybe invest in a bigger SSD instead. |
43 |
> |
44 |
> |
45 |
> I'm currently holding out on my Core2 though, because Haswell is on the |
46 |
> doorstep, and I first wanna see what the market has to offer. The CPU part |
47 |
> might not gain much in performance, but the graphics part got a big boost and |
48 |
> all models support VT-d now (according to cpu-world.com). Plus theoretically |
49 |
> I'm a bit more future-proof due to the new socket (which is probably the most |
50 |
> annoying thing about the Intel world, compared to AMD). |
51 |
> |
52 |
|
53 |
Be very careful. This laptop's processor does not have VT-x...and that |
54 |
bit me. |
55 |
|
56 |
$ cat /proc/cpuinfo |
57 |
processor : 0 |
58 |
vendor_id : GenuineIntel |
59 |
cpu family : 6 |
60 |
model : 42 |
61 |
model name : Intel(R) Pentium(R) CPU B940 @ 2.00GHz |
62 |
stepping : 7 |
63 |
microcode : 0x14 |
64 |
cpu MHz : 800.000 |
65 |
cache size : 2048 KB |
66 |
physical id : 0 |
67 |
siblings : 2 |
68 |
core id : 0 |
69 |
cpu cores : 2 |
70 |
apicid : 0 |
71 |
initial apicid : 0 |
72 |
fpu : yes |
73 |
fpu_exception : yes |
74 |
cpuid level : 13 |
75 |
wp : yes |
76 |
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge |
77 |
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe |
78 |
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl |
79 |
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor |
80 |
ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt |
81 |
tsc_deadline_timer xsave lahf_lm arat epb xsaveopt pln pts dtherm |
82 |
bogomips : 3990.81 |
83 |
clflush size : 64 |
84 |
cache_alignment : 64 |
85 |
address sizes : 36 bits physical, 48 bits virtual |
86 |
power management: |
87 |
|
88 |
processor : 1 |
89 |
vendor_id : GenuineIntel |
90 |
cpu family : 6 |
91 |
model : 42 |
92 |
model name : Intel(R) Pentium(R) CPU B940 @ 2.00GHz |
93 |
stepping : 7 |
94 |
microcode : 0x14 |
95 |
cpu MHz : 800.000 |
96 |
cache size : 2048 KB |
97 |
physical id : 0 |
98 |
siblings : 2 |
99 |
core id : 1 |
100 |
cpu cores : 2 |
101 |
apicid : 2 |
102 |
initial apicid : 2 |
103 |
fpu : yes |
104 |
fpu_exception : yes |
105 |
cpuid level : 13 |
106 |
wp : yes |
107 |
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge |
108 |
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe |
109 |
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl |
110 |
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor |
111 |
ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt |
112 |
tsc_deadline_timer xsave lahf_lm arat epb xsaveopt pln pts dtherm |
113 |
bogomips : 3990.81 |
114 |
clflush size : 64 |
115 |
cache_alignment : 64 |
116 |
address sizes : 36 bits physical, 48 bits virtual |
117 |
power management: |
118 |
|
119 |
|
120 |
Anyway (copying from what I just sent in response to Pandu)... |
121 |
|
122 |
Personally, I've enjoyed both Intel and AMD processors. Last I assembled |
123 |
a system, Intel's midrange offered more bang for the buck than AMD, but |
124 |
Intel's midrange part was also much more expensive. OTOH, AMD systems |
125 |
could be upgraded for piece by piece for much, much, much longer, |
126 |
whereas Intel systems tended to require replacing many more parts at the |
127 |
same time. |
128 |
|
129 |
That was about five years ago, though...I don't know exactly where |
130 |
things sit today. I'd start with the cpubenchmarking.net CPU value |
131 |
listing, and find the best-value part that has the performance degree |
132 |
I'm looking for. |
133 |
|
134 |
http://cpubenchmark.net/cpu_value_available.html |
135 |
|
136 |
I might also cross-reference that page with this one: |
137 |
|
138 |
http://cpubenchmark.net/mid_range_cpus.html |
139 |
|
140 |
If buying an Intel part, I'd be very, very careful to make sure that it |
141 |
supported all the features I want. I've been bit by that on this |
142 |
laptop...I had no idea it wouldn't have VT-x. |