@Hajime said in plot_optimizer_1.6-j6jq:
@zyzzyva Thank you for reply.
So that means I do not need to optimize because I am using XPlotter?
Yes, that's correct.
@Hajime said in plot_optimizer_1.6-j6jq:
@zyzzyva Thank you for reply.
So that means I do not need to optimize because I am using XPlotter?
Yes, that's correct.
Just as a note to anyone else looking for the API docs, the nxtcrypto.org mentioned above seems to be gone. I found the docs at https://nxtwiki.org/wiki/The_Nxt_API.
@Hajime Direct mode is only for the GPU plotter. XPlotter always creates optimized plots.
@rds PlotsChecker only looks at the filename and the length of the file, as far as I know. It doesn't actually look at the nonces themselves. Since XPlotter 1.0 creates a sparse file with the correct length before it starts writing nonces, I don't think PlotsChecker can tell whether all nonces have been written correctly.
@SmartonoseN Right now I'm running jminer on two machines, one with 16GB system RAM and one with 8GB. Oddly enough, I found that the "sweet spot" for chunkPartNonces seemed to be around 960000 on both machines. Beyond that, I didn't get much improvement, and trying much higher values like 1920000 actually got me slightly slower read speeds.
Obviously this is a pretty unscientific test. I'd love to hear other people's results.
@skyline_king88 Are they optimized? If not, you could use the Plot Optimizer tool to optimize them (which will make optimized copies of your plot files), or replot them with XPlotter (which will create an optimized plot file from scratch) if you're low on disk space.
I've been mining various cryptos for years now, sometimes with much sketchier equipment than hard drives (i.e. GPUs, ASICs), and these are my rules of thumb:
Never say never, but I've haven't had a disaster yet while following those rules.
@falconCoin If your wallet isn't on the same machine that you're making the request from, you would need to configure your wallet settings to allow API connections from other hosts (if possible, you should configure it only to allow connections from the host you'll be making requests from, for security). You'll also need to configure it to listen on network interfaces other than localhost.
If you look in the conf/ subdirectory of the wallet source, you'll find a file called nxt-default.properties. You can override variables in that file by creating another file called nxt.properties and putting your configurations in there. I think the relevant variables are nxt.allowedBotHosts and nxt.apiServerHost.
Also, you want to use the URL http://<hostname>:8125/burst, and not port 7876/nxt.
Those are my learnings from playing with some API calls over the weekend, anyway. :) Other devs probably know more.
@rds Cool, I'm gonna give this a try then. I've been failing miserably creating plots bigger than 1TB with gpuPlotGenerator.