What is currently the most profitable coin to mine?
Actually, none
Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 67. (Read 3426930 times)
October 08, 2014, 01:35:55 PM
Actually, none
October 08, 2014, 01:23:55 PM
What is currently the most profitable coin to mine?
I could tell you, but the profit will go down. 
October 08, 2014, 01:02:03 PM
unfortunately they have only one server option, with its port
Oh well, looking at the screenshot you posted, you're not losing big amounts of mining time, so I doubt it will affect your profits that much.
yeah you are right, it was just irritating lol
October 08, 2014, 12:35:15 PM
..now testing x15 on my GTX980. Its hashing with 4.7Mh/s with ccminer m7v7 reliese...
October 08, 2014, 12:31:23 PM
unfortunately they have only one server option, with its port
Oh well, looking at the screenshot you posted, you're not losing big amounts of mining time, so I doubt it will affect your profits that much.
October 08, 2014, 11:24:42 AM
unfortunately they have only one server option, with its port
October 08, 2014, 11:07:57 AM
i'm trying scrypt, and i'm getting this, which shouldn't be normal, others algo work great
Doesn't that happen when the miner switches blocks and there is a delay?
yeah everytime it happen there is "stratum detected a new block"
that delay is from the pool? or is a problemi with my pc?
Most likely somewhere between you and the pool-server, with a possibility of it being the pool itself. Does your pool have multiple regional servers? Then try one of the other servers, preferably closer to your location, perhaps that will solve it.
October 08, 2014, 10:19:48 AM
i'm trying scrypt, and i'm getting this, which shouldn't be normal, others algo work great
Doesn't that happen when the miner switches blocks and there is a delay?
yeah everytime it happen there is "stratum detected a new block"
that delay is from the pool? or is a problemi with my pc?
October 08, 2014, 09:47:08 AM
i'm trying scrypt, and i'm getting this, which shouldn't be normal, others algo work great
Doesn't that happen when the miner switches blocks and there is a delay?
+1 or bad connection with the poolDoesn't that happen when the miner switches blocks and there is a delay?
October 08, 2014, 09:25:51 AM
i'm trying scrypt, and i'm getting this, which shouldn't be normal, others algo work great
Doesn't that happen when the miner switches blocks and there is a delay?
October 08, 2014, 08:59:26 AM
i'm trying scrypt, and i'm getting this, which shouldn't be normal, others algo work great
October 08, 2014, 08:42:56 AM
What is currently the most profitable coin to mine?
Actually, none
He asked for the "most profitable coin", not "a profitable coin" ^^"
October 08, 2014, 08:36:04 AM
What is currently the most profitable coin to mine?
Actually, none
October 08, 2014, 08:24:33 AM
What is currently the most profitable coin to mine?
October 08, 2014, 06:31:45 AM
Get ready for Killer Blake(x11,x13,x15) etc.
Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
does it mean x11 is 400% faster ? Or are you just running on blake privately ? Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
i dont think so. Screen shot show x11 about 3000 kh
(don't sell them yet )Do these improvements also work for older cards, namely CUDA 3.5?
October 08, 2014, 06:30:33 AM
3 months for an optimized blake, we should get the fully optimized x11 in 2years... great
By then new method of mining would already took over GPU mining.
) October 08, 2014, 06:28:13 AM
3 months for an optimized blake, we should get the fully optimized x11 in 2years... great
By then new method of mining would already took over GPU mining.
October 08, 2014, 06:26:32 AM
Get ready for Killer Blake(x11,x13,x15) etc.
Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
does it mean x11 is 400% faster ? Or are you just running on blake privately ? Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
i dont think so. Screen shot show x11 about 3000 kh
(don't sell them yet ) October 08, 2014, 06:20:00 AM
Get ready for Killer Blake(x11,x13,x15) etc.
Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
does it mean x11 is 400% faster ? Or are you just running on blake privately ? Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
i dont think so. Screen shot show x11 about 3000 kh
October 08, 2014, 06:17:14 AM
Get ready for Killer Blake(x11,x13,x15) etc.
Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
does it mean x11 is 400% faster ? Or are you just running on blake privately ? Here are 5'tIs in action with standard clocks mining x11.
I have only optimized the first hash function of the 11 hash'es.
1. Hash rewritten in 100% assembly language and tweaked for the 750 TI
2. Removed latency and improved superscalar performance.
3. Removed stupid code
Note that the blake hash is probobly around 400% faster than ccminer 1.2.
Will keep the miner private for now.
Jump to: