S_tring, Just thought of two other basic things you want to take into consideration: 1) You may want/need a "fudge" factor for some pools or algos. As an Example, you will hardly ever earn the same amount (long term) as a pure math calculator will tell you due to orphons, coin or pool issues. As an example you might earn 5% less on Jackpot then a calc will tell you but you will probably earn 15% less on CryptoNight. So when doing your calculations you would multiple Jackpot * .95 and any CryptoNight coin * .85, etc This type of thing would take into affect pool fees or your could track them separately. You will have to assemble this info as you go but it's worth tracking and adding to your profit switching algo as you go. 2) Make sure you have very, very accurate rates for each hash algo you are going to run. This is the reason I added the average hash rate using the last 50 submitted shares to nvMiner. I found after adding and using this many of my hash rates were not accurate. Some high and some low but it made a difference. If your hash rates are off then everything else will be off of course. Garbage in = garbage out.  Hope this wasn't too much info but I'd consider these the basics of what to track and how to switch to get started. Then you can add additional things and optimize it. Carlo Many thanks for all the advice Carlo, and to others for the earlier suggestions. I definitely need to experiment more. |
|
|
|
|
I'd be interested in opinions on auto profit switching.
If x11 is deemed the most profitable coin, how long should we mine it before checking which coin is best again?
I've set it to check every 60 seconds and switch if necessary. It's been running for 1 hour 10 minutes, and has switched algo 16 times. Too much? Or, maybe it's good to mix the coins so much?
I'm not sure if I should leave a larger interval between scanning for most profitable algo?
|
|
|
|
Getting errors on x15 with djm34 miner... [2014-07-12 16:06:18] GPU #3: result for nonce $9AA1ACB9 does not validate on CPU!
R U getting this just occassionly or all the time? Is it only on GPU3 or all the GPUs? Are your cards OCed? It appears to be occasional, but I'm profit switching via ccManager so it hasn't switched back to x15 since it happened. I'll take it off the profit switching and test later (heading out just now). It was only GPU3 that I noticed. All cards are stock settings. Thanks. |
|
|
|
Due to server costs, Coin Catcher will be closing down in the next couple of days. Please point your miners at another pool to avoid any downtime.
Thanks to all our 1000+ users that got onboard since our launch in February - it was a fun project and it's a shame to have to bring it to an end!
Yep, it was a good pool. Unfortunately, GPU scrypt mining is dead. |
|
|
|
Getting errors on x15 with djm34 miner... [2014-07-12 16:06:18] GPU #3: result for nonce $9AA1ACB9 does not validate on CPU!
|
|
|
|
hey guys
quick question
I'm mining with ccminer and was wondering is it possible to set the worker to close after a time limit has been set?
Windows or Linux? ccManager supports sessions, but it's Linux only. |
|
|
|
anyone like to venture a guess as to why parallaxcoin has 20% higher network hashrate compared to monocle?
MON:
Network Hashrate
2,222.78 MH/sec
PLX:
Network Hashrate
2,627.95 MH/sec
just seems weird as PLX appears to be a dead/abandoned coin...
It must be merge mined by more "partner" coins? |
|
|
|
I'm coding an auto profit switching facility into ccManager. Obviously, it has to switch algos which means it has to switch to the correct miner.
So, am I right in saying that for optimum results...
nist5 = Christian's miner
x11 = Christian's miner
x13 = Christian's miner
x15 = Djm34's miner
Cryptonight = Tsiv's miner
Or you could use the unified version. As far as I know it didn't break anything. No unfortunately I can't, ccManager is written for Linux only. |
|
|
|
|
I'm coding an auto profit switching facility into ccManager. Obviously, it has to switch algos which means it has to switch to the correct miner.
So, am I right in saying that for optimum results...
nist5 = Christian's miner
x11 = Christian's miner
x13 = Christian's miner
x15 = Djm34's miner
Cryptonight = Tsiv's miner
|
|
|
|
I would not use cuda 6.5 until it is officially released and tested. I have seen no difference in performance between 5.5 and 6.0, you need 6.0 to use sm_50 but nothing in ccminer requires that yet.
Your earlier error would appear to be from not having automake installed. Make sure you have everything needed for compiling C++ applications. I am not familiar with the usual setup for this on ubuntu.
Thank you for answering! I've found a website "How to Compile a C/C++ Program on Ubuntu Linux" http://www.wikihow.com/Compile-a-C/C%2B%2B-Program-on-Ubuntu-Linux and it says ... "Open up a terminal on Ubuntu Linux and install the build-essential package by typing the following command in the terminal Type/Copy/Paste: sudo apt-get install build-essential This will install the necessary C/C++ development libraries for your Ubuntu Linux system to create C/C++ programs." ... so probably I will only need the "build-essential" package. Let's see in a few hours You need the Cuda toolkit installed to compile ccMiner. Build essential is not enough on it's own. |
|
|
|
|
There have been too many pool operators with excess MON to dump, and this has kept supply greater than demand. If pool operators are happy to sell at any price just to get rid of the excess coin that they don't want, then the price will continue to fall, no matter what exchange it's on.
How do we expect the algo change to affect things? Does anyone know what the new algo will be?
|
|
|
|
ccManager updated to v0.0.3-alpha  Info and DL link: http://www.coindiscussion.co.uk/forum/viewtopic.php?f=46&t=295#p1743##################################################################
##################################################################
##
## v0.0.3-alpha
## - [CHG] Failover count only shows if there have been failovers
## - [CHG] Updated Readme with additional information
## - [NEW] Used miner now shown in terminal
## - [NEW] Error count now shown in terminal
## - [FIX] Bug fixes
##
##################################################################
##################################################################
|
|
|
|
|
I'm using 1.2 and getting just about the same on a 750Ti.
Failover is achieved with ccManager.
|
|
|
|
Minting info on the icon at the bottom doesn't change. Or it's only my Windows version of wallet has this bug?.. It's more than 24h I get the same numbers Same on Linux, if you restart the wallet it changes. |
|
|
|
How do I get my Linux wallet to stake? It's unlocked and been running for 2 days but no stake.  How many coins do you have? 120k 120k is too low coinage to expect stake interest in 2 days. You need to have 10x more for that time frame ( this was in my case) OK. If my wallet got closed for an hour or so, would my minting revert back to the start again? If in mean time you got your first stake, then it will not revert back. Otherwise unfortunately yes. So just leave your wallet 24/7 open till first stake. Best bet would be if you have it on your mining machine. Just be patient and you'll see rewards afterward. My wallet is now staking like crazy. I trained it well  Just noticed that my estimated time to stake is 19 days. What's the chances I don't need to do a system reboot in that time! I think it's fair to say my wallet will never stake.  No, just keep mining and your balance will grow, thus decreasing the stake time... Anyway forget that time counter in new wallet version. BTW: how may coins do you mine per day? I'm mining around 40k per day. |
|
|
|
How do I get my Linux wallet to stake? It's unlocked and been running for 2 days but no stake. How many coins do you have? 120k 120k is too low coinage to expect stake interest in 2 days. You need to have 10x more for that time frame ( this was in my case) OK. If my wallet got closed for an hour or so, would my minting revert back to the start again? If in mean time you got your first stake, then it will not revert back. Otherwise unfortunately yes. So just leave your wallet 24/7 open till first stake. Best bet would be if you have it on your mining machine. Just be patient and you'll see rewards afterward. My wallet is now staking like crazy. I trained it well Just noticed that my estimated time to stake is 19 days. What's the chances I don't need to do a system reboot in that time! I think it's fair to say my wallet will never stake. |
|
|
|
How do I get my Linux wallet to stake? It's unlocked and been running for 2 days but no stake. How many coins do you have? 120k 120k is too low coinage to expect stake interest in 2 days. You need to have 10x more for that time frame ( this was in my case) OK. If my wallet got closed for an hour or so, would my minting revert back to the start again? |
|
|
|
How do I get my Linux wallet to stake? It's unlocked and been running for 2 days but no stake. How many coins do you have? 120k |
|
|
|
How do I get my Linux wallet to stake? It's unlocked and been running for 2 days but no stake. |
|
|
|
Could some coding guru offer assistance? In bash I can query the GPU temp with: nvidia-smi --query-gpu=temperature.gpu --format=csv,noheader,nounits --id=0 How can I get the GPU temperature in C++ |
|
|
|
|
Show Posts
