Actually both typically increase when overclocking.
The poster probably meant that you can run a higher Vcore without as much concern for the increased temperature that results (from the increased current).
For those who don't know, you typically run a higher Vcore when overclocking a system in order to improve stability (i.e. in order to ensure that CPU signals can still ramp up/ramp down to valid voltages quickly enough at the faster clock rate).
For those who know more than I, please feel free to correct me or elaborate where I've oversimplified.
Whenever your code has occasion to store a boolean value (for later test/comparison), store multiple copies of it at predictable but "geographically" disparate locations in RAM.
Then, when doing the test/comparison, if there is not consensus in the bits (they should be all 1 or all 0), you know some memory error has occurred. The confidence level in the boolean test could be made arbitrarily high by storing increasing numbers of redundant bits.
This would slow things down considerably but it seems cheaper than lead cases.
This countermeasure is obviously not foolproof because most branches ultimately come down to a single register test but perhaps it's an improvement? Comments?
I think you should go to the media with this, but first you should consider running a few queries on the data, such as a proximity search for twenty-something nymphomaniacs in your province.
DNS is supposed to provide nameIP mappings, in an application-neutral fashion.
Yes, and the Internet was intended to be a means for scientists and military personnel to exchange information, and HTML was intended to link cross-referenced scientific documents.
My point is, you can nitpick details about the existing protocols/DNS record types and for what they were originally intended but that doesn't mean it's the wrong type of architecture.
If you were building a system from the ground up to be a mirror directory for various well-known services it would probably end up looking a bit like DNS in its hierarchy (and probably, semantics).
That being said, I think the parent post's idea is problematic in more significant regard in that it tries to assign a standard meaning to an unstandardized record type which could only wreak chaos with DNS servers that did not support it.
I think a more "correct" approach could involve adding an additional record type to DNS that enumerated available mirrors for a host's well-known services that were listed in its WKS records. It could return results similar to an MX query (service [e.g. ftp], host name, priority) along with port and country information.
OK, I will comment on this. I live in Sunnyvale and (knock on wood) have been continuously employed as a software engineer for the 7 years I've been out of school.
"Very good coders" are not in short supply, and in the Bay Area, an MCSE or Cisco certification is as illustrative of potential value to a company as, say, a driver's license. Same goes for quantity of resume buzzwords, which only carry a premium when hype is king, which now unfortunately it is not.
The start-ups doing best in this are lean (principals and architects only) and outsource a lot of work to places like Bulgaria and Bangalore.
The people doing best in this area have breadth, depth, experience building services, experience shipping products, experience managing teams, communication ability, and of course (of course), connections.
And those of us who meet the above criteria but don't have 6+ figures in the bank (from either prudent savings or a stint at a dot-com that actually went public), well, we are still pretty nervous.
Housing prices are finally starting to come down to earth though, and knock on wood I'll be able to buy a 1600sq.ft. 3/2 house in a relatively nice neighborhood in Sunnyvale for less than $550K come summer.
You might think about buying an 802.11b-enabled handheld PC (I think the cheapest run about $600), some voice-over-IP server software, and a bunch of commodity 802.11b equipment that you can sprinkle all around BFE.
Then, get your hands on (or develop if you're so inclined) a voice-over-IP telephone client for said handheld PC and server software.
Seems like this could work as a poor man's makeshift wireless phone service. Of course I have no idea how graceful 802.11b equipment is about handing off from access point to access point, but it seems a lot cheaper (if less entertaining) than Profane Motherfucker's solution.
Slashdot Mirror
The poster probably meant that you can run a higher Vcore without as much concern for the increased temperature that results (from the increased current).
For those who don't know, you typically run a higher Vcore when overclocking a system in order to improve stability (i.e. in order to ensure that CPU signals can still ramp up/ramp down to valid voltages quickly enough at the faster clock rate).
For those who know more than I, please feel free to correct me or elaborate where I've oversimplified.
Then, when doing the test/comparison, if there is not consensus in the bits (they should be all 1 or all 0), you know some memory error has occurred. The confidence level in the boolean test could be made arbitrarily high by storing increasing numbers of redundant bits.
This would slow things down considerably but it seems cheaper than lead cases.
This countermeasure is obviously not foolproof because most branches ultimately come down to a single register test but perhaps it's an improvement? Comments?
I think you should go to the media with this, but first you should consider running a few queries on the data, such as a proximity search for twenty-something nymphomaniacs in your province.
Since doughnuts can be deformed from coffee cups, it explains why caffeine makes my world go around.
My point is, you can nitpick details about the existing protocols/DNS record types and for what they were originally intended but that doesn't mean it's the wrong type of architecture.
If you were building a system from the ground up to be a mirror directory for various well-known services it would probably end up looking a bit like DNS in its hierarchy (and probably, semantics).
That being said, I think the parent post's idea is problematic in more significant regard in that it tries to assign a standard meaning to an unstandardized record type which could only wreak chaos with DNS servers that did not support it.
I think a more "correct" approach could involve adding an additional record type to DNS that enumerated available mirrors for a host's well-known services that were listed in its WKS records. It could return results similar to an MX query (service [e.g. ftp], host name, priority) along with port and country information.
"Very good coders" are not in short supply, and in the Bay Area, an MCSE or Cisco certification is as illustrative of potential value to a company as, say, a driver's license. Same goes for quantity of resume buzzwords, which only carry a premium when hype is king, which now unfortunately it is not.
The start-ups doing best in this are lean (principals and architects only) and outsource a lot of work to places like Bulgaria and Bangalore.
The people doing best in this area have breadth, depth, experience building services, experience shipping products, experience managing teams, communication ability, and of course (of course), connections.
And those of us who meet the above criteria but don't have 6+ figures in the bank (from either prudent savings or a stint at a dot-com that actually went public), well, we are still pretty nervous.
Housing prices are finally starting to come down to earth though, and knock on wood I'll be able to buy a 1600sq.ft. 3/2 house in a relatively nice neighborhood in Sunnyvale for less than $550K come summer.
Then, get your hands on (or develop if you're so inclined) a voice-over-IP telephone client for said handheld PC and server software.
Seems like this could work as a poor man's makeshift wireless phone service. Of course I have no idea how graceful 802.11b equipment is about handing off from access point to access point, but it seems a lot cheaper (if less entertaining) than Profane Motherfucker's solution.