No benchmarks permitted.

So...how do we set up to bench mark and illegality publish our results?

"Aint that the way it ought'a be?
 
Personally I love Intel chips. But it would be nice if I wasn't always the last to know when they blow it. Has anyone ever been contacted by Intel to be warned of a flaw? It seems like a computer company could manage that doesn't it?
 
Big Business really loves to keep its mistakes and flaws under wraps. After all "the business of America is business," said that great (not so much) president Calvin Coolidge.
But the problem is that the business of America RUNS the government.
Could we be in more caring hands?

"In good hands with Allstate." Yeah, yeah. Sure, sure.

Must I add imho? Why not.
 
At this point I'd like to try and involve our more advanced users. Folks are talking about disabling hyper-threading in ones BIOS. This to avert the effects of Intel Micro code vulnerabilities.

This seems a bit radical. Can someone put this in perspective for me?
1. How vulnerable am I as an average user?
2. Is it worth the up to 30% hit in performance to guard against this vulnerability?

Should I blame turrmmy or is this a French thing?
 
It would be wonderful if intelligent actions could save us. It's not impossible. However those in charge, and it ain't we the people last time I looked, sincerely want all the good for themselves. Which leaves the 99% of us?

I know, I know, ask Mr Market.

Oh, oh. I'm not an advanced user. Sorry.
 
Daniel~ said:
At this point I'd like to try and involve our more advanced users. Folks are talking about disabling hyper-threading in ones BIOS. This to avert the effects of Intel Micro code vulnerabilities.

This seems a bit radical. Can someone put this in perspective for me?
1. How vulnerable am I as an average user?
2. Is it worth the up to 30% hit in performance to guard against this vulnerability?

Should I blame turrmmy or is this a French thing?
Click to expand...

30% is rather extreme; for most workloads the hit is much lower, particularly for user workloads, although it likely will still run in the realm of 10 - 15%, based on what I've read.

The likelihood of having your PC compromised by this is essentially 0; it's not (at least currently) a way to get malware on your computer. It IS a way to steal information OFF your computer; passwords, account information, that sort of thing. However, the only successful demonstrations of these attacks that I am aware of required something like HOURS to get BITS of data.

As a matter of prudence, anyone running a server with sensitive information should make sure they have all patches and BIOS updates applied. Depending on the sensitivity of the information, they may also want to disable hyper-threading.

For ordinary users.........well, let me put it this way........<I'M> not going to disable HT, and I imagine that I am more paranoid than most. I've applied the patches and the BIOS updates, and for my day-to-day operations, I haven't noticed a significant performance impact. As always, your mileage may vary.
 
You must log in or register to reply here.
Back
Top