Author

Topic: The network just hit 40 PetaFLOPS! (Read 1957 times)

hero member
Activity: 644
Merit: 503
May 23, 2011, 03:18:02 PM
#14
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.
sr. member
Activity: 406
Merit: 257
May 22, 2011, 08:35:10 PM
#13
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.
sr. member
Activity: 406
Merit: 250
May 22, 2011, 08:26:55 PM
#12
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.
member
Activity: 112
Merit: 10
May 22, 2011, 08:20:08 PM
#11
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.
sr. member
Activity: 406
Merit: 250
May 22, 2011, 08:17:17 PM
#10
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.
member
Activity: 112
Merit: 10
May 22, 2011, 08:09:05 PM
#9
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?
legendary
Activity: 2968
Merit: 1198
May 22, 2011, 07:23:46 PM
#8
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.
full member
Activity: 154
Merit: 100
hero member
Activity: 644
Merit: 503
May 22, 2011, 06:20:02 PM
#6
Why are you measuring hashes/s in FLOPS?
I assume it's because bitcoinwatch shows TeraFLOP/s (as well as Gigahashs/s).
sr. member
Activity: 308
Merit: 250
May 22, 2011, 06:17:12 PM
#5
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.
sr. member
Activity: 966
Merit: 254
May 22, 2011, 06:12:33 PM
#4
Why are you measuring hashes/s in FLOPS?
What else would you measure it in?
newbie
Activity: 29
Merit: 0
May 22, 2011, 06:01:59 PM
#3
Why are you measuring hashes/s in FLOPS?
Xer
member
Activity: 99
Merit: 10
May 22, 2011, 05:51:27 PM
#2
So, Skynet next?
full member
Activity: 154
Merit: 100
May 22, 2011, 05:12:12 PM
#1
All Your Base Are Belong To Us!!!!!!!!!
Jump to: