Get a voltmeter, place the black lead on ground and the read lead on the power lead of the chip. 1.5 Volts going in. Check.
Now move the red lead to the other power lead on the chip - Zero volts coming out! Where are these volts going? But it not accurate to say they are being *consumed* per se. The volts are stored in the form of magic smoke. When the chip is full of volts (as magic smoke), it stops working. Be careful, too many volts going in and you can burst the smoke tank, then you're really screwed!
(While performing this test, don't let the amps leak out of the power supply and onto the...um... ground)
By the way, flash has a slight weird characteristic that you can write to it with a byte granularity, but only erase it with a block granularity, and it's the number of erases that cause the problems.
Does "erasing" mean "make zero"? If so what's the difference between "erasing" at the block level and "writing" zeros at the byte-level? Is block-level writing/erasing faster than multiple individual byte-level writes? I'm sure it's trivial to implement some logic that can pick the more approriate operation.
And at the same time, the Diesel engine gives you much more power at lower speed (that is, everything up to the speed limit
Please study and understand the relationship between Power, RPM, torque, gearing, and road speed.
Diesel engines provide more torque at a lower engine RPM but they provide less torque at higher engine RPM. Because of gearing (in the transmission), this is independent of road speed. Power is Torque*RPM (ignoring units). If you use gearing to increase the torque 10x, you reduce the speed 10x and end up at the same power - same thing applies if you increase the speed 10x and reduce the torque 10x through gearing.
However, it doesn't work that well for large apps that get parallelized across multiple CPUs. It turns out that most code, and most compilers, are good at splitting tasks in two - or in powers of two - so having three CPUs is no faster than having two.
The third processor can run supporting thread(s) that control the "worker" threads. Let alone support processes such as network, I/O, or anything else in the OS - leaving the two CPUS (and their caches) wide(r) open for application crunching.
Because the American automaker execs are too busy spending time and money lobbying against efficiency and emissions legislation to actually have the time and money to do R&D for efficiency and emissions improvements?
It was. Let me help you here...
The OP said that it crashed on his non-mainstream OS so I made an obscure, and some might even say clever, reference to another non-mainstream/obsolete OS.
See how that works? Neat, huh?
Didn't you read the headline? You can't stop these things. Heck, the demo popped up an unkillable window on my AmigaOS box, and no JVM even exists for that...
It seems to me that AMD is always a step behind in implementing a new generation of SSE instructions and that causes them to lose a lot of benchmarks, especially games. If SSE(x) instructions have to be implemented in an OS, aren't they a type of standard that any chip manufacturer can implement? Or are they created by Intel and only through licensing/agreements available for the likes of AMD to implement?
Slashdot Mirror
Two words: Clippy Core
Get a voltmeter, place the black lead on ground and the read lead on the power lead of the chip. 1.5 Volts going in. Check.
...um... ground)
Now move the red lead to the other power lead on the chip - Zero volts coming out! Where are these volts going? But it not accurate to say they are being *consumed* per se. The volts are stored in the form of magic smoke. When the chip is full of volts (as magic smoke), it stops working. Be careful, too many volts going in and you can burst the smoke tank, then you're really screwed!
(While performing this test, don't let the amps leak out of the power supply and onto the
Capitalism rewards manipulative wheeler-dealers far more than creativity. It rewards those who can best exploit creative ideas, not make them.
And that's why we have patents!
Oh...wait...nevermind....
Score: -1, Turd ?? :^P
Hook multiple USB drives up in RAID and there won't be any CPU power left to do the thing you need all that data for!
When I told a charming, beautiful young woman she could plug into my public API, I got slapped!
Probably because you didn't expose an Adapter Class interface!
...license agreements!
But given that the UK and US are on the same hemisphere...
:^P
Aren't virtually *any* two places on the globe in the "same hemisphere"?
Yes, I know you meant "Northern hemisphere", but your post prompted the thought.
...clitorus-foreheaded space-aliens...
Geez, some guys can't even find it in the dictionary!
(But I'll give you credit, that's a funny term!)
Do you people have any idea how hard it is to teach astronomy when half the class snickers every time the 7th planet is mentioned?
In light of the public's growing familiarity with anatomy and diminishing mental age, the IAU should rename Uranus.
I heard the IAU is considering "Urasshole"...
By the way, flash has a slight weird characteristic that you can write to it with a byte granularity, but only erase it with a block granularity, and it's the number of erases that cause the problems.
Does "erasing" mean "make zero"? If so what's the difference between "erasing" at the block level and "writing" zeros at the byte-level? Is block-level writing/erasing faster than multiple individual byte-level writes? I'm sure it's trivial to implement some logic that can pick the more approriate operation.
And at the same time, the Diesel engine gives you much more power at lower speed (that is, everything up to the speed limit
Please study and understand the relationship between Power, RPM, torque, gearing, and road speed.
Diesel engines provide more torque at a lower engine RPM but they provide less torque at higher engine RPM. Because of gearing (in the transmission), this is independent of road speed. Power is Torque*RPM (ignoring units). If you use gearing to increase the torque 10x, you reduce the speed 10x and end up at the same power - same thing applies if you increase the speed 10x and reduce the torque 10x through gearing.
...and Merge files. I would stay away from the last one.
What's Why wrong not with merge merging files files automatically?
Actually, 42 cores is the answer.
However, it doesn't work that well for large apps that get parallelized across multiple CPUs. It turns out that most code, and most compilers, are good at splitting tasks in two - or in powers of two - so having three CPUs is no faster than having two.
The third processor can run supporting thread(s) that control the "worker" threads. Let alone support processes such as network, I/O, or anything else in the OS - leaving the two CPUS (and their caches) wide(r) open for application crunching.
Because the American automaker execs are too busy spending time and money lobbying against efficiency and emissions legislation to actually have the time and money to do R&D for efficiency and emissions improvements?
<slashdot class="FirstPost"> (deprecated)
<slashdot class="Dupe">
<slashdot class="LibrariesOfCongress">
<slashdot class="BeowulfCluster">
It was. Let me help you here... The OP said that it crashed on his non-mainstream OS so I made an obscure, and some might even say clever, reference to another non-mainstream/obsolete OS. See how that works? Neat, huh?
Didn't you read the headline? You can't stop these things. Heck, the demo popped up an unkillable window on my AmigaOS box, and no JVM even exists for that...
No kidding, I got a TOS Error #35!
I ran the text through google translate and this is what happened
Odd, when I ran it through, I got this...
"Google buys AT&T, changes name to AT&T."
It seems to me that AMD is always a step behind in implementing a new generation of SSE instructions and that causes them to lose a lot of benchmarks, especially games. If SSE(x) instructions have to be implemented in an OS, aren't they a type of standard that any chip manufacturer can implement? Or are they created by Intel and only through licensing/agreements available for the likes of AMD to implement?
Here
What's next, being ordered to "log" the electrical signals on your phone line?
...back in my day we had to LOGIN to school. And LOGOUT , too! Typing, with both hands each way!
Have these guys who wrote the summary heard of the Heisenberg uncertainty principle?
Yes, but as soon as they heard of it, they couldn't locate it.