The network just hit 40 PetaFLOPS!

[epi 1:10,000]

All Your Base Are Belong To Us!!!!!!!!!

[1714925937]

1714925937

[1714925937]

1714925937

[1714925937]

1714925937

[1714925937]

1714925937

[Xer]

So, Skynet next?

[jarly]

Why are you measuring hashes/s in FLOPS?

[Convery]

Why are you measuring hashes/s in FLOPS?

What else would you measure it in?

[Quantumplation]

What else would you measure it in?

... Hashes per second?  1 FLOP is Float Operation, and there are many float operations per hash, so it's kind of a misleading unit of measurement when talking about network performance.

[LMGTFY]

Why are you measuring hashes/s in FLOPS?

I assume it's because bitcoinwatch shows TeraFLOP/s (as well as Gigahashs/s).

[epi 1:10,000]

So, Skynet next?

The land of Oz is building Skynet

http://www.cio.com.au/article/387097/exclusive_ska_bid_looks_skynet_computing/

Bitcoin v. SkyNet v. Folding

[smooth]

Why are you measuring hashes/s in FLOPS?

I assume it's because bitcoinwatch shows TeraFLOP/s (as well as Gigahashs/s).

What does that even mean?  There is no floating point in hashing.

[1bitc0inplz]

Why are you measuring hashes/s in FLOPS?

because hashes/sec is meaning outside of Bitcoin. If we want to know how big the network is versus a super computer, what else would you measure it in?

[xenon481]

Why are you measuring hashes/s in FLOPS?

because hashes/sec is meaning outside of Bitcoin. If we want to know how big the network is versus a super computer, what else would you measure it in?

Integer Operations and Floating Point Operations are not comparable.

[1bitc0inplz]

Integer Operations and Floating Point Operations are not comparable.

Of course... but then the whole hash/sec on Bitcoin Watch is an estimate anyway...

So, when you get down to it, all these numbers are meaningless.

However, knowing a rough ballpark of a FLOPs rate *is* interesting, because it does help you think in scale of the TOP 500.

[xenon481]

Integer Operations and Floating Point Operations are not comparable.

Of course... but then the whole hash/sec on Bitcoin Watch is an estimate anyway...

So, when you get down to it, all these numbers are meaningless.

However, knowing a rough ballpark of a FLOPs rate *is* interesting, because it does help you think in scale of the TOP 500.

But you can't actually assume any kind of estimate of how many FLOPs our network is. If I can do 2 Integer operations in one clock but only Floating Point operation per clock, you can't just say my 8 million integer operations per second are the equivalent of 8MFLOPS. Some hardware can even do 4 Integer operations in the same time it takes to do one single Floating Point operation.


Edit: For hashing, the proper network computational power unit is MIPS instead of FLOPS.

[ArtForz]

I get about half that assuming vast majority of hashrate is ATI 5xxx GPUs.
3Thps = about 8300 5870s = about 22.5PFLOPS peak single precision, 4.5PFLOPS peak double precision.

[LMGTFY]

Why are you measuring hashes/s in FLOPS?

I assume it's because bitcoinwatch shows TeraFLOP/s (as well as Gigahashs/s).

What does that even mean?  There is no floating point in hashing.

It means exactly what I said: that bitcoinwatch displays TeraFLOP/s as well as Gigahashs/s. I have no idea why; you'd need to ask them.