Pages:
Author

Topic: [ANN][SHC] ShinyCoin █First ever RAMHOG algo Pow/Pos █NO ASIC/GPU | Whitepaper - page 29. (Read 58444 times)

full member
Activity: 625
Merit: 100
Does anybody think this title will be better?Huh?


   [ANN] [SHC] ShinyCoin █First ever RAMHOG algo  Pow/Pos  █ NO ASIC/GPU | Whitepaper | No Premine/IPO
legendary
Activity: 966
Merit: 1009
Pool got really unlucky, we missed the block diff by like 10-20% 7 times in a row
Edit: quick pool maintenance... - And we are back up!

I can't understand what happened.

Something is wrong between block 2123 and 2157
hero member
Activity: 616
Merit: 500
Pool got really unlucky, we missed the block diff by like 10-20% 7 times in a row
Edit: quick pool maintenance... - And we are back up!
hero member
Activity: 616
Merit: 500
Shinyminer source: https://github.com/siklon/shinyminer

Code:
git clone https://github.com/siklon/shinyminer
cd shinyminer
./autogen.sh
./configure CFLAGS="-Ofast -funroll-loops"
make
./minerd -o stratum+tcp://106.3.225.46:6666 -O SWVcv2ByWmriwD4X97bEUhnooHww6qR2at:x -t 1

That's cool! Have you tested it or is this a call for testing?

If you mine to a wallet instance instead of that IP, does it work?


No its not working. He is working with the dev to fix it.

Compiled the source with: "-Ofast -funroll-loops"

On an EC2 r3.8xlarge instance (32 cpu vcores, 244GB ram), mines with 15 ramhog threads at ~110 hashes/min (7.3 hashes/min/thread):

Code:
[2014-06-26 16:03:31] accepted: 1/1 (100.00%), 109.20 hash/m (yay!!!)

Is it good or bad hashrate compared to the boxes you have tried?


I have been doing some testing on the EC2 and I found that the smaller Memory optimized instances are more efficient than the larger ones.

The r3.8xlarge gives between 107-110 hash/m and costs around 0.256$
The r3.4xlarge gives between 62-65 hash/m and costs around 0.128$
The r3.2xlarge gives between 36-40 hash/m and costs around 0.064$

I didn't check the r3.xlarge as you are limited to 5 instances in each region when you are using spot instances but my guess is that it is even more efficient. You would just need a lot of them to match the larger servers.

So clearly 4 x r3.2xlarge would be a better option than 1 x r3.8xlarge in relation to hash per $ as for the same cost you would get 144-160 hash/m while the single r3.8xlarge would only give you 107-110 hash/m

Hope this helps Smiley


I tested them all. It is exactly as you say. r3.2xlarge is the most efficient box taking into account the spot instance limits.


I forgot, add flag -march=native to get a processor specific binary, should be faster.
member
Activity: 111
Merit: 10
Can some one please make a guide how to compile shinycoin-qt under Ubuntu and what dependancy must install.
hero member
Activity: 616
Merit: 500
Quote
[2014-06-27 18:12:18] Stratum connection timed out
[2014-06-27 18:12:18] Stratum connection interrupted

Pool is broken?

Nope, just a little overloaded.

15000ms latency now...

Should be faster now, made some changes...

Because of the 280 confirmations and the currently small p2p network, it takes a while to send out payments. Just make sure redis does not lose its data under any circumstances or, in case it loses it, it can be recovered from the log file or from a dump. This is the only thing that really worries me about the pool. Smiley



There are hourly backups for redis.
hero member
Activity: 616
Merit: 500
Quote
[2014-06-27 18:12:18] Stratum connection timed out
[2014-06-27 18:12:18] Stratum connection interrupted

Pool is broken?

Nope, just a little overloaded.

15000ms latency now...

Should be faster now, made some changes...
legendary
Activity: 1092
Merit: 1000
Quote
[2014-06-27 18:12:18] Stratum connection timed out
[2014-06-27 18:12:18] Stratum connection interrupted

Pool is broken?

Nope, just a little overloaded.

15000ms latency now...
hero member
Activity: 616
Merit: 500
Quote
[2014-06-27 18:12:18] Stratum connection timed out
[2014-06-27 18:12:18] Stratum connection interrupted

Pool is broken?

Nope, just a little overloaded.
legendary
Activity: 966
Merit: 1009
Quote
[2014-06-27 18:12:18] Stratum connection timed out
[2014-06-27 18:12:18] Stratum connection interrupted

Pool is broken?
sr. member
Activity: 330
Merit: 252
Another thing I have noticed is that even if you lower down the amout of threads running on the EC2's you still keep the same amount of hashrate. You just get more hash/m on each thread instead.

Like on the r3.8xlarge. I got the same amount of hash/m if I was using 8 or 10 threads as when I was using 15 threads.



CPU power... I am maxing out 8 core i7 4770 with only two threads.

i7 4770 is not a real 8core... 4 cores = 8HT. -t 2 threads should be best option with 32GB ram, so this should be true what our two faced "friend" said  Wink
I have some i7 4930K with 32gb ram... 6cores = 12HT. -t 2 is the best option and gives 43h/s. I would need more ram to go further.

full member
Activity: 625
Merit: 100
1.  Official website
2.  Beautiful Logo
3.  Exchange request
4.  CoinMarketCap add request
5.  Can you modify this thread title into :

   [ANN] [SHC] ShinyCoin █First ever RAMHOG algo  Pow/Pos  █ NO ASIC/GPU | Whitepaper | No Premine/IPO
full member
Activity: 138
Merit: 100
I lost 1100 ACN, http://minin.gs/acn/

Wmsoc1f1EjKVeJceBxg2dGeRMuqUbj6PMabHXwioy2QqUy2vxVqM18LTPibZUknoWHi2RzyzejCF6d1 7FHtz2a6n1bWLVhsec
sr. member
Activity: 269
Merit: 250
sr. member
Activity: 258
Merit: 250
Another thing I have noticed is that even if you lower down the amout of threads running on the EC2's you still keep the same amount of hashrate. You just get more hash/m on each thread instead.

Like on the r3.8xlarge. I got the same amount of hash/m if I was using 8 or 10 threads as when I was using 15 threads.



CPU power... I am maxing out 8 core i7 4770 with only two threads.

Yeah.. definitly the main factor when you get past the 15GB mem requirements.

How much are you getting from your maxed i7 4770?



32-37

Nice. Did you try to OC to see what kind of improvements it gives?

legendary
Activity: 1092
Merit: 1000
Another thing I have noticed is that even if you lower down the amout of threads running on the EC2's you still keep the same amount of hashrate. You just get more hash/m on each thread instead.

Like on the r3.8xlarge. I got the same amount of hash/m if I was using 8 or 10 threads as when I was using 15 threads.



CPU power... I am maxing out 8 core i7 4770 with only two threads.

Yeah.. definitly the main factor when you get past the 15GB mem requirements.

How much are you getting from your maxed i7 4770?



32-37
sr. member
Activity: 258
Merit: 250
Another thing I have noticed is that even if you lower down the amout of threads running on the EC2's you still keep the same amount of hashrate. You just get more hash/m on each thread instead.

Like on the r3.8xlarge. I got the same amount of hash/m if I was using 8 or 10 threads as when I was using 15 threads.



CPU power... I am maxing out 8 core i7 4770 with only two threads.

Yeah.. definitly the main factor when you get past the 15GB mem requirements.

How much are you getting from your maxed i7 4770?

legendary
Activity: 1092
Merit: 1000
Another thing I have noticed is that even if you lower down the amout of threads running on the EC2's you still keep the same amount of hashrate. You just get more hash/m on each thread instead.

Like on the r3.8xlarge. I got the same amount of hash/m if I was using 8 or 10 threads as when I was using 15 threads.



CPU power... I am maxing out 8 core i7 4770 with only two threads.
sr. member
Activity: 258
Merit: 250
Another thing I have noticed is that even if you lower down the amout of threads running on the EC2's you still keep the same amount of hashrate. You just get more hash/m on each thread instead.

Like on the r3.8xlarge. I got the same amount of hash/m if I was using 8 or 10 threads as when I was using 15 threads.

legendary
Activity: 1092
Merit: 1000
We need moooooooore amazon cloud suckers mining this coin so once it hits an exchange they dont dump for peanuts!  Grin
Pages:
Jump to: