GPU Miners are here... if rumors are to be believed!

[reorder]

Is that actually HPM, as in hashes per minute, or collisions per minute (which coyote miner prints as hpm for some reason)?

Coyote: collisions per minute reported as hpm (at least on github which is 12 days old! - the binary probably multiplies this by 2 also, otherwise coyote miner would be two times slower)
Beeer and ypool: collisions per minute * 2 reported as col/m

Which one is it?

edit:
http://bitsharestalk.org/index.php?topic=965.0
Ok, so 520HPM is impossible on amazon instance. So it's actually col/m*2 for all public miners.

So unless you specifically modified a miner to report true hpm you're getting 500 col/m. Did you?

It is real hpm, or cpm*2.

[iruu]

Is that actually HPM, as in hashes per minute, or collisions per minute (which coyote miner prints as hpm for some reason)?

Coyote: collisions per minute reported as hpm (at least on github which is 12 days old! - the binary probably multiplies this by 2 also, otherwise coyote miner would be two times slower)
Beeer and ypool: collisions per minute * 2 reported as col/m

Which one is it?

edit:
http://bitsharestalk.org/index.php?topic=965.0
Ok, so 520HPM is impossible on amazon instance. So it's actually col/m*2 for all public miners.

So unless you specifically modified a miner to report true hpm you're getting 500 col/m. Did you?

[Brekyrself]

~3x improvement in hpm...When can we have it?

[reorder]

huh? now was any of that real? can we see some vid of it working at least?

Sorry, I hate it when a helicopter does not explode in a movie, and do not have a spare helicopter at hand. Now, if you find this amusing, here is how it looks like:

Code: [Select]

Sun Nov 24 22:21:29 2013 Worker 0 505.567078 hpm  --> Upstream RPC result: True
Sun Nov 24 22:21:30 2013 Worker 0 505.573132 hpm  --> Upstream RPC result: True
Sun Nov 24 22:21:31 2013 Worker 1 504.408057 hpm  --> Upstream RPC result: True
Sun Nov 24 22:21:33 2013 Worker 1 504.419294 hpm  --> Upstream RPC result: True
Sun Nov 24 22:21:34 2013 Worker 1 504.401926 hpm  --> Upstream RPC result: True
Sun Nov 24 22:21:34 2013 Worker 0 505.529154 hpm  --> Upstream RPC result: True
Not even a mining porn, really.

[mitao]

Open source in one week?


Sent from my iPhone using Tapatalk

[lordfirefox]

I suck at programming math, otherwise I'd make one myself.

[KrzysiekT]

I agree that finding collisions by GPU should be simple to implement in use (maybe by some OpenCL lib), however I thought than performance boost will be larger. Still, there's few optimalization tricks that can be deployed, but need some time consuming work, and diff is rising so fast now.

PS. Sudden impact of GPU miners and farms will raise diff pretty exponential. I suggest buy some shares if that's topic isn't fake

[atp1916]

^^ Links clearly look valid and not scammy at all.  Especially that image link. 

[reorder]

Python is significantly slower than C.  Buyer beware.  Personally i would wait for a C implementation than buy a python one.

Sorry, but so what? You do not need ultra performance to send 10-20 packets of data/sec over network Most pools are running python, for that matter.

Anyway, sold.

EDIT: sold exclusively.

Right, and i should take whatever a salesman says at face value too.  There's a reason that all decent miners are written in C, and it certainly can't be hand-waved away by some silly argument about network performance.

Not selling anymore, but still. There are multiple reasons for that indeed, speed being not on the list. Think poclbm and how it is still alive and well.

[doesntmatter]

huh? now was any of that real? can we see some vid of it working at least?

[crendore]

Python is significantly slower than C.  Buyer beware.  Personally i would wait for a C implementation than buy a python one.

Sorry, but so what? You do not need ultra performance to send 10-20 packets of data/sec over network Most pools are running python, for that matter.

Anyway, sold.

EDIT: sold exclusively.

Right, and i should take whatever a salesman says at face value too.  There's a reason that all decent miners are written in C, and it certainly can't be hand-waved away by some silly argument about network performance.

[m0rph]

Python is significantly slower than C.  Buyer beware.  Personally i would wait for a C implementation than buy a python one.

Sorry, but so what? You do not need ultra performance to send 10-20 packets of data/sec over network Most pools are running python, for that matter.

Anyway, sold.

Price? )))

[Vizierx]

Python is significantly slower than C.  Buyer beware.  Personally i would wait for a C implementation than buy a python one.

Sorry, but so what? You do not need ultra performance to send 10-20 packets of data/sec over network Most pools are running python, for that matter.

Anyway, sold.

Price? )))

[reorder]

Python is significantly slower than C.  Buyer beware.  Personally i would wait for a C implementation than buy a python one.

Sorry, but so what? You do not need ultra performance to send 10-20 packets of data/sec over network Most pools are running python, for that matter.

Anyway, sold.

EDIT: sold exclusively.

[crendore]

Python is significantly slower than C.  Buyer beware.  Personally i would wait for a C implementation than buy a python one.