It isn't so much that underclocking will give you the benefits, but undervolting.
Power, if I could remember the damn equation through this cold, is depending on voltage^3.
Lowering the frequency will allow you to use less volts to keep the transistor stable. Underclock, and lower the voltage, test the stability. Find a undervolted value that you like, cook it with a stress test for 24 hours or so, and then watch the difference.
The rest of your reply after 0.25% doesn't really apply because this is a phone, using an ARM chip that doesn't provide nearly comparable power to a desktop.
As an previous end user of a Symbian phone, the phone was slow. It started up programs slowly, it handled task switching slowly. That's the part that matters to the end user, not stats and arguments made with the modern desktop hardware in mind.
And this is part of the reason why I stopped using my Nokia N82. The other part was that it crashed so damn often when I'm using gmail and opera. To add insult to injury, microkernels are suppose to allow more graceful crashes of kernel level components.When gmail / opera crash, it's white screen, and the only input that it would take would be to power off, and then to power on. So where's the microkernel advantage here? Clearly something was wrong with the network code, otherwise it wouldn't have crashed like that. But I don't exactly call a pure white screen with no options but to power-cycle "graceful handling of crashes".
One of the most overlooked computer problems are faulty power supplies that cannot give power near what the specs says.
CPU may be the brains of the computer, but the power supply is the heart, supplying vital electricity to all the component. Too often, I've worked on machines where as soon as I plug in a cheapo tester, nothing lights up as the proper voltage, yet the machine still manages to "run".
That could possibly be monitored with software, if the BIOS supports voltage monitoring.
They have been endangering my bank account and my credit rating for years. Half the time they release books that suck, at ridiculous prices, and since the bookstore doesn't have a used copy, I end up paying for the full price. Textbooks that are worth their sticker price are rare. The majority of the text aren't worth half of that sticker price.
It is a rather poor explanation... But their compressor is catered to executables, so that it transmit a sort of primitive assembly language, so that the diffs are smaller, transmit that, and have the client end to apply and reassemble.
So their compression algorithm has little applications outside of executables.
Are you trying to get experience so that you are more marketable in the job market? If so, and you're in a post-secondary, try internship / co-operative education. If you just want to program for the sake of programming, try contributing to an existing project. If you're trying to learn how to run one, start a project.
This is by no means the definitive way to do things, nor correct, but I think you get the idea.
Try RTFA. The attack is against AES-256, which although the attack is still theoretical, 2^119 is more than collapsing the keylength to less than half its original size.
That actually doesn't look too good, because as pointed out by Scheier, attacks are only going to get better.
If your book's already being distributed illegally, that means that a) you've got good info that people want, or at least a professor use your book and b) people didn't care to fork out money for the paper copy, or they don't want a paper copy.
You can create your book, without the publisher and distribute on line without the cost of going to the printing press, for much less. I'd easily fork over $10 for a good digital copy of a book.
In that case, you're equally screwed if you bought a batch that are out of spec, at 7pm on a Wednesday night, and your boss needed that server wired up a few hours ago. I don't think the boss would say, "Oh. Belkin screwed up, let's wait til tomorrow when we can replace this whole batch with something in-spec".
I'd say, keep a spool around, do what he says, and if shit hits the fan, at least you could make one long enough to replace the out-of-spec one.
I'm a cynic, and although I'm not a tree-hugger, I much prefer not dumping at where we eat.
But really, wind and solar has scale problems, and highly dependent of the weather for a stable output. Hydro is a bit more stable, but like the first two, they're not immune from politics.
You'd think outdoor enthusiasts like hikers and such would be for renewable energy (and they are), but they won't like it too much if you stick a bunch of windmills at their favourite hiking spots, with good reason. Access roads need to be built, and the natural setting would be devalued because we're trying to be green.
Hydro's even worse in terms of the politics - them hippie tree huggers wants green power without any alteration of the natural environment. All of these renewable energy sources requires some level of it, and for the nuclear plants, no one's a fan of the waste.
Even if Shell isn't an oil company, I can see why someone would want to pull out of the business. There's just way too much crap to put up with even get some kind of consensus out there about what's good for us and good for where we live.
So, L4D sales grew 30x when you cut the price in half, and this is a game that I'm willing full price, and 2 more to gift 3 other copies (the 4 pack at the price of 3).
It's bloody rare for a game to actually be worth $50. No one want to sink that money on a game that people aren't sure is that fun. At $25, I think that barrier is less, and if people are fans, and rave about it, more would buy it / gift it.
Facebook screws around their site live so often that it is not even sensible to assume that their site is running properly if you can point your browser to it.
In a 4 month stint as a maintenance programmer for one of the apps on there, it has become impossible to tell when I introduced a bug onto the app, or Facebook is actually crapping out.
I would laugh if once we factor that in, it suffers more outages than Twitter.
sigh. something got cropped. The Vanguard got damaged props, while the Le Triomphant had a damaged sonar dome (i.e. damaged front). This can mean the Le Triomphant was a the rear of the Vanguard while the collusion occurred...
Althought I agree with your assessment, the interesting part is that the HMS Vanguard was towed back to port, while the French counterpart suffered sonar dome damage. One plausible explanation is that the Vanguard has damaged props, while
As quiet as these subs are, the sonar dome on Le Triomphant should pick up screws in the water, at close ranges.
A more sinister explanation would be the Le Triomphant was tailing the Vanguard, and they ran into the Vanguard when the British sub slowed/stopped. They aren't going to explain to the public that a friendly nation's nuclear sub has been tailing our sub all along.
Maybe having the ballpark at $13k is good enough. Maybe having the Red in a pixel at 240 is good enough compared to 255. But how is the chip going to tell that making a jump to 0x389519B0 - some offset requires full precision, compared to, I dunno subtracting this number because someone punched it into the calculator program.
And at the end, CPUs calculate a lot of these integers for indexed jumps, and branches very frequently. How's the hardware going to be able to tell when it can skimp and when it cannot?
When it can't, it would be trying to run linux on known bad ram. Things will crash, and people won't be happy. If you need software to hint, then you might be able to code a compiler to do it for you, but even then, the people who knows which addition need full precision and which one doesn't is the application designer. The compiler won't read your minds.
If they say, they'd split this into 2 sets of arithmetic instruction, then they're not going to get the power efficiency they were looking for anyways.
Sometimes the Event Viewer is a bit of a hit and miss, but if there's anything big from Windows that's crapping out, it should log something in the Event Viewer.
Check Control Panel -> Administrative Tools -> Event Viewer.
Using visible light is actually highly impractical too. Imagine some cleaner got annoyed by the damn blinkenlight, and put something to block it, and never got around to removing it.
There are plenty of problems that can demonstrate to a young mind how to think like the machine, without the need of a "learner's language".
A good chunk of people who I've seen struggle at programming simply can't think like a programmer, and they would fail at any language that you give them.
Programming is a mind set, the language is just implementation detail.
I don't necessarily agree that an engineer should set the requirements in stone before coding. Although proper planning is a must, having the flexibility to deal with changing requirements is probably more useful.
Remember, clients are whimsical people who don't know anything about software development, or the technologies (and the associated limitations) that you'll be using. And they don't really care what problems you'll run into. They want their problems solved, and you're the one to fix it.
Slashdot Mirror
It isn't so much that underclocking will give you the benefits, but undervolting.
Power, if I could remember the damn equation through this cold, is depending on voltage^3.
Lowering the frequency will allow you to use less volts to keep the transistor stable. Underclock, and lower the voltage, test the stability. Find a undervolted value that you like, cook it with a stress test for 24 hours or so, and then watch the difference.
The rest of your reply after 0.25% doesn't really apply because this is a phone, using an ARM chip that doesn't provide nearly comparable power to a desktop.
As an previous end user of a Symbian phone, the phone was slow. It started up programs slowly, it handled task switching slowly. That's the part that matters to the end user, not stats and arguments made with the modern desktop hardware in mind.
And this is part of the reason why I stopped using my Nokia N82. The other part was that it crashed so damn often when I'm using gmail and opera. To add insult to injury, microkernels are suppose to allow more graceful crashes of kernel level components.When gmail / opera crash, it's white screen, and the only input that it would take would be to power off, and then to power on. So where's the microkernel advantage here? Clearly something was wrong with the network code, otherwise it wouldn't have crashed like that. But I don't exactly call a pure white screen with no options but to power-cycle "graceful handling of crashes".
One of the most overlooked computer problems are faulty power supplies that cannot give power near what the specs says.
CPU may be the brains of the computer, but the power supply is the heart, supplying vital electricity to all the component. Too often, I've worked on machines where as soon as I plug in a cheapo tester, nothing lights up as the proper voltage, yet the machine still manages to "run".
That could possibly be monitored with software, if the BIOS supports voltage monitoring.
They have been endangering my bank account and my credit rating for years. Half the time they release books that suck, at ridiculous prices, and since the bookstore doesn't have a used copy, I end up paying for the full price.
Textbooks that are worth their sticker price are rare. The majority of the text aren't worth half of that sticker price.
It is a rather poor explanation...
But their compressor is catered to executables, so that it transmit a sort of primitive assembly language, so that the diffs are smaller, transmit that, and have the client end to apply and reassemble.
So their compression algorithm has little applications outside of executables.
Are you trying to get experience so that you are more marketable in the job market? If so, and you're in a post-secondary, try internship / co-operative education.
If you just want to program for the sake of programming, try contributing to an existing project.
If you're trying to learn how to run one, start a project.
This is by no means the definitive way to do things, nor correct, but I think you get the idea.
Seems like NSA is constructing a much bigger site according to the Salt Lake Tribune.
Try RTFA. The attack is against AES-256, which although the attack is still theoretical, 2^119 is more than collapsing the keylength to less than half its original size.
That actually doesn't look too good, because as pointed out by Scheier, attacks are only going to get better.
NSA can't guarantee that they're collecting American citizens' email, even if they try.
Anyone want to propose a solution?
If your book's already being distributed illegally, that means that a) you've got good info that people want, or at least a professor use your book
and b) people didn't care to fork out money for the paper copy, or they don't want a paper copy.
You can create your book, without the publisher and distribute on line without the cost of going to the printing press, for much less. I'd easily fork over $10 for a good digital copy of a book.
In that case, you're equally screwed if you bought a batch that are out of spec, at 7pm on a Wednesday night, and your boss needed that server wired up a few hours ago. I don't think the boss would say, "Oh. Belkin screwed up, let's wait til tomorrow when we can replace this whole batch with something in-spec".
I'd say, keep a spool around, do what he says, and if shit hits the fan, at least you could make one long enough to replace the out-of-spec one.
So, extra work, extra machines/VM needs to be in place to get this done.
Plus depending on how old/cheap the workstations are, the onboard NIC may not have wake-on-lan feature anyways.
Like those CEOs who are making a reaping despite the bad economy opening some rootkit and exposing information. That's a legit worry.
If an IT guy is going to turn bad, they would've done that a long time ago. They're in the best position to avoid detection anyways.
I use a Das II, and I wish I could bring it to work.
I grew up playing the piano, and the tactile feedback is really great. This membrane keyboard crap blows for typing anything correctly.
I'm a cynic, and although I'm not a tree-hugger, I much prefer not dumping at where we eat.
But really, wind and solar has scale problems, and highly dependent of the weather for a stable output. Hydro is a bit more stable, but like the first two, they're not immune from politics.
You'd think outdoor enthusiasts like hikers and such would be for renewable energy (and they are), but they won't like it too much if you stick a bunch of windmills at their favourite hiking spots, with good reason. Access roads need to be built, and the natural setting would be devalued because we're trying to be green.
Hydro's even worse in terms of the politics - them hippie tree huggers wants green power without any alteration of the natural environment. All of these renewable energy sources requires some level of it, and for the nuclear plants, no one's a fan of the waste.
Even if Shell isn't an oil company, I can see why someone would want to pull out of the business. There's just way too much crap to put up with even get some kind of consensus out there about what's good for us and good for where we live.
So, L4D sales grew 30x when you cut the price in half, and this is a game that I'm willing full price, and 2 more to gift 3 other copies (the 4 pack at the price of 3).
It's bloody rare for a game to actually be worth $50. No one want to sink that money on a game that people aren't sure is that fun. At $25, I think that barrier is less, and if people are fans, and rave about it, more would buy it / gift it.
Facebook screws around their site live so often that it is not even sensible to assume that their site is running properly if you can point your browser to it.
In a 4 month stint as a maintenance programmer for one of the apps on there, it has become impossible to tell when I introduced a bug onto the app, or Facebook is actually crapping out.
I would laugh if once we factor that in, it suffers more outages than Twitter.
sigh. something got cropped. The Vanguard got damaged props, while the Le Triomphant had a damaged sonar dome (i.e. damaged front). This can mean the Le Triomphant was a the rear of the Vanguard while the collusion occurred...
Althought I agree with your assessment, the interesting part is that the HMS Vanguard was towed back to port, while the French counterpart suffered sonar dome damage. One plausible explanation is that the Vanguard has damaged props, while
As quiet as these subs are, the sonar dome on Le Triomphant should pick up screws in the water, at close ranges.
A more sinister explanation would be the Le Triomphant was tailing the Vanguard, and they ran into the Vanguard when the British sub slowed/stopped. They aren't going to explain to the public that a friendly nation's nuclear sub has been tailing our sub all along.
Maybe having the ballpark at $13k is good enough. Maybe having the Red in a pixel at 240 is good enough compared to 255. But how is the chip going to tell that making a jump to 0x389519B0 - some offset requires full precision, compared to, I dunno subtracting this number because someone punched it into the calculator program.
And at the end, CPUs calculate a lot of these integers for indexed jumps, and branches very frequently. How's the hardware going to be able to tell when it can skimp and when it cannot?
When it can't, it would be trying to run linux on known bad ram. Things will crash, and people won't be happy. If you need software to hint, then you might be able to code a compiler to do it for you, but even then, the people who knows which addition need full precision and which one doesn't is the application designer. The compiler won't read your minds.
If they say, they'd split this into 2 sets of arithmetic instruction, then they're not going to get the power efficiency they were looking for anyways.
Sometimes the Event Viewer is a bit of a hit and miss, but if there's anything big from Windows that's crapping out, it should log something in the Event Viewer.
Check Control Panel -> Administrative Tools -> Event Viewer.
Using visible light is actually highly impractical too. Imagine some cleaner got annoyed by the damn blinkenlight, and put something to block it, and never got around to removing it.
And it's so not secure, as topham has said.
The piece wasn't even Slashdot worthy.
Or a problem solver, or a computing scientists.
There are plenty of problems that can demonstrate to a young mind how to think like the machine, without the need of a "learner's language".
A good chunk of people who I've seen struggle at programming simply can't think like a programmer, and they would fail at any language that you give them.
Programming is a mind set, the language is just implementation detail.
Guess the Canadian Passport uses the same software?
I don't see what is the big deal, other than the whole biometric tracking thing.
I don't necessarily agree that an engineer should set the requirements in stone before coding. Although proper planning is a must, having the flexibility to deal with changing requirements is probably more useful.
Remember, clients are whimsical people who don't know anything about software development, or the technologies (and the associated limitations) that you'll be using. And they don't really care what problems you'll run into. They want their problems solved, and you're the one to fix it.