One thing on the performance side for intel chips; using hyperthreading kills performance on some tasks because it results in more cache flushes, so you can
sometimes get better performance when turning hyperthreading off, but this is very application dependent. if you have a multi-core chip never use
hyperthreading since you will see almost no gains but can see hughe hits in performance for practically all real applications.
This behavior is not often seen in benchmarks because most benchmarks take great pain to test things in isolation, ie: they do their best to avoid cache misses
when looking at how fast the CPU is, and they try to cause cache misses during the cache test.
For real world applications however the bottleneck is the most important part and cache is often the bottleneck.
E: "Did they... did they just endorse the combination of the JSDF and US Army by showing them as two lesbian lolicons moving in together and holding hands and talking about how 'intimate' they were?"
B: "Have you forgotten so soon? They're phasing out Don't Ask, Don't Tell."
sometimes get better performance when turning hyperthreading off, but this is very application dependent. if you have a multi-core chip never use
hyperthreading since you will see almost no gains but can see hughe hits in performance for practically all real applications.
This behavior is not often seen in benchmarks because most benchmarks take great pain to test things in isolation, ie: they do their best to avoid cache misses
when looking at how fast the CPU is, and they try to cause cache misses during the cache test.
For real world applications however the bottleneck is the most important part and cache is often the bottleneck.
E: "Did they... did they just endorse the combination of the JSDF and US Army by showing them as two lesbian lolicons moving in together and holding hands and talking about how 'intimate' they were?"
B: "Have you forgotten so soon? They're phasing out Don't Ask, Don't Tell."