 Show Posts
|
|
Pages: [1]
|
Can I run the software in demo mode and see what it behaves like before I purchase?
There is an option in config file which is call: Testmode enable that and you will be able to test the market without risking your real balance This is not however, paper trading. It will test the buy strategy, but not the sell strategy from what I understand. |
|
|
|
|
I know I'm a newbie here, but let me just say that I just bought this bot yesterday solely based on the community. The discord communities (official, CryptoGnome's, and Crypto Crow's - to a lesser extent) around this bot are amazing at sharing information, tweaking settings, sharing settings that work and even sharing screenshots of profits made. Check out CrytpoGnome and Crypto Crow's YouTube videos and you can learn the ins and outs of the program and they even share their setting for free. If you are new to bot trading, like I am, this is great place to start.
I will try to update how things are going from time to time in case anyone is interested.
|
|
|
|
I did not get Airdrop. I did the retweet and filled out the form. Why?  Pretty sure I saw the dev on discord state that the airdrop was closed, but had not been distributed yet. Look for it sometime this week. |
|
|
|
I see a problem with the recently added always updating "benchmark" results: when you add or remove GPUs after you've done the benchmarks the results get messed up, as the currently running algos will change in values, whereas others will not. especially when adding GPUs this will move the current top algo(s) up ahead above the others so they never run again and therefore also don't update their results.
maybe an option to disable the updating after benchmarks could be added?
I think a better solution would be to delete your current benchmarks and re-bench everything when you make a hardware change.. That way you would have the most up to date accurate info out there... in principle yes -- but since accurate benchmarking takes like 6 hours this is not a practical solution. I'm not talking about major architecture changes (like adding new/different GPU types), but simply adding or removing a card of the same type -- so hashing speed simply scales over all algos. since obtaining GPUs for reasonable prices is extremely difficult now I'm simply adding them when I get them. so a rig running (and benchmarked) with three 1070ti might get another 1070ti added once a week until the rig is full. re-running the benchmarks every time is just not practical and also a loss of profits. Ok, so if you are frequently adding cards of the same types, and are expecting the same hash rate, then just go in and manually adjust the benchmarks yourself when you add a new card. Then MM will update the hash rate to more accurately reflect the actual performance of the cards as the algos are called (since we all know that the same cards can have +/-10% performance depending on the silicon lottery). |
|
|
|
I see a problem with the recently added always updating "benchmark" results: when you add or remove GPUs after you've done the benchmarks the results get messed up, as the currently running algos will change in values, whereas others will not. especially when adding GPUs this will move the current top algo(s) up ahead above the others so they never run again and therefore also don't update their results.
maybe an option to disable the updating after benchmarks could be added?
you can just rename your current gpu groups, then it will have to benchmark them again. For example I use a group with 3x1070 (devices 0,1,2), if I want to game on my card that has a display on it, i just copy a different config.txt where I have a group named 2x1070 with devices 1,2 EDIT: that said, I was also wondering about what to do when I change the overclock on my cards, I sometimes run them at 64-75% power limit (when I sleep I want them quiter), and sometimes at 75-89% PL, so hashrate changes a little, so when downclocking it's more probable it will change algos more often, while when upclocking, it will change algos less. For that scenario, I would just have 2 instances of MegaMiner installed on my PC. One that is run at night that keeps all its own benchmarks on the lower power setup, and one that runs in the day with the higher power. |
|
|
|
@tutulfo: About the new feature you are developing.
I think that it will be great if MM can check and apply the best settings for a card. Currently i mine with less power and some overclocked settings (1080 Card), however some algorithms/coins can handle this better as others. Should be nice if MM can handle this fully automated, for me it is difficult to determine the best settings for all coins.
Since everyone's system is different, I don't see a way he would be able to implement that. What you can do is tweak each algo to achieve what you want (highest hash, most efficient, or some balance), save each as an afterburner profile, and then modify the json for each miner (if you wanted it by algo instead of miner, you would need to create a "custom" miner for each algo). You will put something like: "C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe" -profile1
into the "PrelaunchCommand":"", line, so it would look like this: "PrelaunchCommand":"C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe -profile1", Disclaimer: I don't actually use this feature, so I may be a little off base on the format of the command. But it should get you started at least. Edit to add what I meant by adding a custom miner- For example, if C11 needed profile 1 and lbry needed profile 2, what you would do is create a file named N-ccminerAlexis-c11.json that looks like this: {
"Path" : ".\\Bin\\NVIDIA-Alexis78\\ccminer-alexis78-ms2013-cuda7.5\\ccminer.exe",
"ExtractionPath" : ".\\Bin\\NVIDIA-Alexis78\\",
"Uri" : "https://github.com/nemosminer/ccminer-Alexis78/releases/download/ccminer-alexis78/ccminer-alexis78-ms2013-cuda7.5.7z",
"Types" : ["NVIDIA"],
"Arguments" : "-o #PROTOCOL#://#SERVER#:#PORT# -u #LOGIN# -p #PASSWORD# -R 10 -r 4 -b #APIPORT# -d #DEVICES# #ALGORITHMPARAMETERS# ",
"API" : "Ccminer",
"Fee" : 0,
"Wrap" : false,
"Dualmining":false,
"APIPort" : 4068,
"PrelaunchCommand":"C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe -profile1",
"Algorithms": [
{"c11" : "-a c11 -i 20" },
]
}Then add another one named N-ccminerAlexis-lbry.json that looks like this: {
"Path" : ".\\Bin\\NVIDIA-Alexis78\\ccminer-alexis78-ms2013-cuda7.5\\ccminer.exe",
"ExtractionPath" : ".\\Bin\\NVIDIA-Alexis78\\",
"Uri" : "https://github.com/nemosminer/ccminer-Alexis78/releases/download/ccminer-alexis78/ccminer-alexis78-ms2013-cuda7.5.7z",
"Types" : ["NVIDIA"],
"Arguments" : "-o #PROTOCOL#://#SERVER#:#PORT# -u #LOGIN# -p #PASSWORD# -R 10 -r 4 -b #APIPORT# -d #DEVICES# #ALGORITHMPARAMETERS# ",
"API" : "Ccminer",
"Fee" : 0,
"Wrap" : false,
"Dualmining":false,
"APIPort" : 4068,
"PrelaunchCommand":"C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe -profile2",
"Algorithms": [
{"lbry" : "-a lbry" },
]
}And so on. You could also group them by profile (make a N-ccminerAlexis-profile1.json for all the algos that would use profile 1 etc...). |
|
|
|
I see a problem with the recently added always updating "benchmark" results: when you add or remove GPUs after you've done the benchmarks the results get messed up, as the currently running algos will change in values, whereas others will not. especially when adding GPUs this will move the current top algo(s) up ahead above the others so they never run again and therefore also don't update their results.
maybe an option to disable the updating after benchmarks could be added?
I think a better solution would be to delete your current benchmarks and re-bench everything when you make a hardware change.. That way you would have the most up to date accurate info out there... |
|
|
|
SNIP
Love the signatures. Now to just get my newbie account up to a level that I can use them  . |
|
|
|
Couple of quick questions (or depending on the answers suggestions):
1. I auto switch between several pools and I like the 24 hour stats from zpool.ca, but MPH doesn't offer that option, so if i want to autoswitch between those two pools I have to set it to automatic. Is there a way to have it attempt the 24 hour stats but if it isn't available to default back to auto?
2. Is there a way to specify some algos to NOT mine? So if I wanted to mine everything except one or two do I have to list out all the ones I am willing to mine?
I thougth about it last release, next release I will change modes: Automatic: 24h if exists else "now mode" Automatic24h: actual 24h mode AutomaticNow: actual Automatic mode Also I want to change parameters for a section in config file to define launch configurations (I think is easier than parameters) Why not just fallback Automatic24h to Automatic when 24h is not available? clarity, if I do this you can think you are mining with 24h data but is no real. Modify pool file to allow this is really easy, you only need set profit24h to same value than profit on final set and change $ActiveOnAutomatic24hMode=$true A little confused by what you mean. So in Mining_Pool_Hub.ps1 I should change this line from this: $ActiveOnAutomatic24hMode = $false To this: $ActiveOnAutomatic24hMode = $true and this one: Price24h = $null #MPH not send this on api to this: Price24h = $MiningPoolHub_Price Is that right? |
|
|
|
|
Couple of quick questions (or depending on the answers suggestions):
1. I auto switch between several pools and I like the 24 hour stats from zpool.ca, but MPH doesn't offer that option, so if i want to autoswitch between those two pools I have to set it to automatic. Is there a way to have it attempt the 24 hour stats but if it isn't available to default back to auto?
2. Is there a way to specify some algos to NOT mine? So if I wanted to mine everything except one or two do I have to list out all the ones I am willing to mine?
|
|
|
|
|
I just have to say, I have tried multi pool miner, nemo's and Megaminer, and Megaminer is by far the best. Keep up the great work!
|
|
|
|
|
