the question is how long will they mine with the chip before selling it to people (and at what price).
I see Bitmain is presently shipping batch #9 of S7. Or maybe just about to start, they said Jan. 20-30. During the Chinese Spring Festival holiday, no shipments will be made from Feb. 4th to Feb 14th. Shipments will resume on Feb. 15th, they say. I was talking about bitfury, not bitmain.
|
|
|
the question is how long will they mine with the chip before selling it to people (and at what price).
|
|
|
Hello! I've been away from this thread for long, sorry if I'm posting boring stuff now. I've started mining xmr again (for the fun of it). I'm using Wolf0's opensource miner and stock clocks. Getting 678 H/s on 290x and 687 H/s on Fury, are these good hashrates?
|
|
|
long story short: if it's GPL, you can't close source it, unless you have written permission by all the authors (they are relicensing it for you).
|
|
|
people just don't understand that a a chicken tomorrow is better than an egg today. they don't see the bigger picture and want the money right away.
|
|
|
It didn't take long to hit a brick wall with windows.
static inline void transform(cubehashParm *sp )
Expected '(' to follow 'inline'
WTF?
I guess that settles it.
visual studio or mingw?
|
|
|
coin pumps ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) , turn on miner ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) , pump ends ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) , mined coins at original price before pump ![Angry](https://bitcointalk.org/Smileys/default/angry.gif) pumps do not last, hence why (to profit on them) you need to BUY not MINE. how many coins would you have mined in the pump period, anyway? ;-)
|
|
|
Wolf0 I've found the issue. Fiji doesn't want to run with libopencl from APP SDK 3.0. Fiji now works but it's slower than Hawaii, guess HSM is to blame.
|
|
|
For example, I semi-recently not only did the ONLY open-source implementation of a CryptoNight AMD miner, but I didn't base it on existing code infected with the GPL. This means there's now a base that's not only open, but MIT/BSD licensed to work off of for others. Kudos to you! Thank you. Please, if you wish to, use that base publicly or privately for your own miner work - or take bits and pieces from it. A nice guy caught an oversight that I made - I should have used a pthread condition variable and didn't - so now the miner uses pretty much 0% CPU. I'm rather happy and proud that the rest of it was so nice and light. I'll have a look as well, thanks for sharing and shame on me for not noticing it earlier ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Found this runtime issue: [15:54:44] Error -6 when calling clCreateCommandQueueWithProperties. [15:54:44] Error -36 when calling clEnqueueWriteBuffer to fill input buffer. EDIT: looks like it doesn't like the Fiji card but hashes fine on the Hawaii. Works on mine. What's your settings file look like? { "Algorithms": [ { "name": "CryptoNight", "devices": [ { "index": 0, "threads": 1, "rawintensity": 1336, "worksize": 16 }, { "index": 1, "threads": 1, "rawintensity": 1336, "worksize": 16 } ], "pools": [ { "url": "XXXXXXXXXX", "user": "XXXXXXXXXXXX", "pass": "x" } ] } ] }
|
|
|
For example, I semi-recently not only did the ONLY open-source implementation of a CryptoNight AMD miner, but I didn't base it on existing code infected with the GPL. This means there's now a base that's not only open, but MIT/BSD licensed to work off of for others. Kudos to you! Thank you. Please, if you wish to, use that base publicly or privately for your own miner work - or take bits and pieces from it. A nice guy caught an oversight that I made - I should have used a pthread condition variable and didn't - so now the miner uses pretty much 0% CPU. I'm rather happy and proud that the rest of it was so nice and light. I'll have a look as well, thanks for sharing and shame on me for not noticing it earlier ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Found this runtime issue: [15:54:44] Error -6 when calling clCreateCommandQueueWithProperties. [15:54:44] Error -36 when calling clEnqueueWriteBuffer to fill input buffer. EDIT: looks like it doesn't like the Fiji card but hashes fine on the Hawaii.
|
|
|
What's with all the vanillacoin talk? It's not profitable to mine and has FPGAs working for it right now.
It's changing algo. it's now on blake so a quick FPGA work ;-)
|
|
|
joblo, does your quark optimisation work at the end? not sure I understand your conversation with sp_ fully: where does the +30% come from?
|
|
|
64 cores with aes is a good start ;-) I wonder how they perform in cryptonight.
|
|
|
I think we are finding too little blocks. Can't just be bad luck.
|
|
|
Thanks Joblo, I'll test release 3.0.5 later today :-)
|
|
|
SP will you be incorporating the new vanilla blake algo into ccminer? If so, when?
Blake is already included. ccminer -a blake --benchmark or ccminer -a blakecoin --benchmark I don't think it'll work. You should import a little patch which was submitted to tpruvot ccminer a couple days ago. EDIT: "Algo is the same Blake256 8-rounds. It's just different from Blakecoin who's using single sha256 for the merkle root generation. Vanilla will use standard double sha256."
|
|
|
Honestly I don't think it makes any noticeable difference. Initialisation is a very little part of the whole hash computation.
|
|
|
Even more (x11):
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
Did you get that from Wolf0's cryptonight? Yet another thing to look into is all those compiler switches. Some are obvious by their name but other I have no clue, yet. Some from Wolf0, some I found myself, some I don't remember... Some are included into the generic -O optimisation switch: the best to try are -O3 and -Ofast. The defines could be integrated into the code as defaults, if they benefit most cpus.
|
|
|
Even more (x11):
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
|
|
|
a little speedup by better compiling:
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz AES_NI: No. SSE2: No, start mining without optimizations... [....] [2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Think any of this would help me to get a completion compile on the problem AMD system I posted about a few pages back? https://bitcointalk.org/index.php?topic=1326803.msg13657053#msg13657053the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?
|
|
|
|