|
|
|
|
|
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
morantis
|
 |
January 27, 2017, 03:48:43 AM |
|
i have a question. i just downloaded jminer for burst coin and the config file is huge. it looks like for pool mining there are only three variables that need to be set. the files reads really odd. there is an explanation for each parameter given in a comment. the way my line breaks are, it looks like the parameter is set right after the comment, but i think that is not the case, as i see the parameters more clearly used later in the file. the question is this. if i only need to set three parameters in the file, are there other settings in there that are used. can i just make a new config file that contains nothing other than the three parameters and use it or is the included file more important. i know coding and i can read through the file line by line, but would rather avoid that and get it moving more quickly edit:creating my own config file using this method. i started with these three parameters, plotPaths=D:/,C:/,E:/plots,F:/plots
numericAccountId=<YOUR NUMERIC ACCOUNT ID>
poolServer=http://pool.com:port Then I started the script and got an info/error saying that a wallet server is not defined. I will set everything one at a time using the errors that the software spits out. I think this is a nice way of seeing each and every piece of info the software uses and better understanding the program. I will post a final config file that was created using this method here for the info of others. |
|
|
|
|
|
morantis
|
|
January 27, 2017, 04:19:54 AM |
|
until the block chain gets fully synced for me locally and on some other sites i will have no real answer here. I removed the parameters i added for a wallet server because the software claimed to not be able to get mining info. it now works, my dl info is displayed on the pool, but the software is pissed because the mining info is not being reported to it correctly.
once my local wallet is fully recovered from the mess over the past few days, i will point jminer at it for mining info. to test jminer i only used a drive that has 200 GB plotted on it and i am not impressed at the results versus the regular mining software. i saw a dl of a year, and another in the 9 month range. I am using the same pc to plot at this moment, so that could be an issue.
once i am locally snyced and i have stopped my current plotting, i will try it for an hour with all my plots and then use uray's for an hour with the same plots and report back here. it seems that the software can and will run with only the three parameters set, setting a walletserver via the config can do nothing but improve things.
|
|
|
|
|
|
morantis
|
|
January 27, 2017, 01:17:10 PM |
|
ok, pretty significant difference. i use s very simple conf file that i will tweak over time. plotPaths=D:/Burst/plots,C:/Burst/plots,E:/Burst/plots
numericAccountId=xxxxxxx
poolServer=http://pool.burstcoin.uk:80
walletServer=https://wallet.burst-team.us:8125 i will go through the original one line at a time and through the github help and see if i can use any other parameters to improve things. but it seems that the gpu miner jminer versus the other cpu miners i have used shows a good 50% or greater increase in production. it is hard to gauge exactly, as this is a new rig, building from the bottom up and i switched to the jminer at the same time that i nearly doubled the plot sizes. but, compared the the same rig that is already running and the time when it had the same amount of plots/sizes there is a big difference |
|
|
|
|
|
luxe (OP)
|
|
January 27, 2017, 06:45:03 PM |
|
@morantis Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page. As far as i can see you did everything correctly ... But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did. The walletServer is only used to get the last winner and not relevant for mining at all. There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.propertiesJust want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup. Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc. So nice to see your interest, play arround and ask if something is not clear ... This thread was not very active due to the fact that burst has a very active forum, and most ask questions there ( https://forums.burst-team.us). |
|
|
|
|
|
morantis
|
|
January 28, 2017, 06:55:28 AM |
|
@morantis Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page. As far as i can see you did everything correctly ... But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did. The walletServer is only used to get the last winner and not relevant for mining at all. There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.propertiesJust want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup. Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc. So nice to see your interest, play arround and ask if something is not clear ... This thread was not very active due to the fact that burst has a very active forum, and most ask questions there ( https://forums.burst-team.us). it is very possible that it was my screen resolution combined with the word wrap, but literally the "example" of each parameter fell directly on the next line and character 1, appearing to a coder like me as a line of code outside of a comment block, lol. that is what led to most of my confusion was not realizing that lines were part of the preceding line as a remark so what i saw was something like this //you can use the message method to include a private message, this is set later in this code, nearly 40 lines later, lol
message='why did these words wrap at EXACTLY the wrong space break'
.....and much later
//here is the setting of the message method as spoke about before
message='and here i am AGAIN, i imagine, since it is Java that this is the one going to the Jar, as it is the last one in the code block, but feel free to set the variable as many times as you like, lol'
//end code block that my pc got a kick out of formatting is the PERFECT way to confuse
|
|
|
|
|
|
luxe (OP)
|
|
January 28, 2017, 09:01:47 AM |
|
@morantis Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page. As far as i can see you did everything correctly ... But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did. The walletServer is only used to get the last winner and not relevant for mining at all. There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.propertiesJust want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup. Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc. So nice to see your interest, play arround and ask if something is not clear ... This thread was not very active due to the fact that burst has a very active forum, and most ask questions there ( https://forums.burst-team.us). it is very possible that it was my screen resolution combined with the word wrap, but literally the "example" of each parameter fell directly on the next line and character 1, appearing to a coder like me as a line of code outside of a comment block, lol. that is what led to most of my confusion was not realizing that lines were part of the preceding line as a remark so what i saw was something like this //you can use the message method to include a private message, this is set later in this code, nearly 40 lines later, lol
message='why did these words wrap at EXACTLY the wrong space break'
.....and much later
//here is the setting of the message method as spoke about before
message='and here i am AGAIN, i imagine, since it is Java that this is the one going to the Jar, as it is the last one in the code block, but feel free to set the variable as many times as you like, lol'
//end code block that my pc got a kick out of formatting is the PERFECT way to confuse
I understand ... i will think about how to improve that .... I was using notepad++ or comparable to edit jminer.properties and therefore i did not see, that this may be a issue. For me it looks like this ...  |
|
|
|
|
|
luxe (OP)
|
|
May 25, 2018, 09:22:27 PM |
|
[burstcoin-jminer-0.5.1-SNAPSHOT]Download: https://github.com/de-luxe/burstcoin-jminer/releasesNotice: burstcoin-jminer-0.5.x supports both, POC1 and POC2 plotfiles. This will also be the case after the fork. However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used. The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork. - Only use one type, POC1 or POC2 on one drive ('plotPath'), mixed will be skipped. - Ensure your POC2 plotfiles do not have staggersize in filename , or they will be treated like POC1. - Read speed is calculated by plotsize, so if jminer reads twice the data on e.g. POC2 pre-fork, the numbers displayed will not be accurate.
|
|
|
|
|
|
luxe (OP)
|
|
May 30, 2018, 08:15:57 PM |
|
[burstcoin-jminer-0.5.2-RELEASE]Download: https://github.com/de-luxe/burstcoin-jminer/releasesNotice: Supports both, POC1 and POC2 plotfiles. This will also be the case after the fork. However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used. The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork. - Only use one type, POC1 or POC2 on one drive ('plotPath'), mixed will be skipped. - Ensure your POC2 plotfiles do not have staggersize in filename , or they will be treated like POC1.
|
|
|
|
|
|
luxe (OP)
|
|
July 19, 2018, 02:22:16 PM
Last edit: July 19, 2018, 02:54:20 PM by luxe |
|
[burstcoin-jminer-0.5.3-SNAPSHOT]Download: https://github.com/de-luxe/burstcoin-jminer/releasesUpdates: - #72 jminer crashes if a plot file is actively being plotted - #73 listPlotFiles=true does not always show list - improved re-start round after wallet fork handling - prevent concurrent modification while creating real capacity lookup - ensure lowestCommitted does not get updated with higher committed deadline due to bad timing - removed obsolete properties triggerServer, recommitDeadlines, poc2ActivationBlockHeight - some code cleanup and update to latest libs
|
|
|
|
|
|
