I went ahead and tested plotting with 8 separate instances. It does seem to be a little faster overall (about a 7% improvement). Think I'll leave it to plot. Thanks for the help guys, looks like we have gotten it down to around 12 days which is a reasonable improvement.
nathanowen42
@nathanowen42
Posts made by nathanowen42
-
RE: 600 Hours to Plotposted in Mining & Plotting
-
RE: 600 Hours to Plotposted in Mining & Plotting
Okay, I have pulled the raid card, switched to Windows 10 and set everything up. Do you think it is faster to run xplotter with 8 threads one drive at a time, or would it be faster to run 8 separate xplotter instances (1 per drive) with one thread each.
-
RE: 600 Hours to Plotposted in Mining & Plotting
Is there an advantage to using xplotter over mdcct?
-
600 Hours to Plotposted in Mining & Plotting
I am just getting into burstcoin mining.
I tried to get gpuPlotGenerator (https://github.com/bhamon/gpuPlotGenerator) working on linux with an Nvidia GTX770 but I always get '[ERROR][-36][CL_INVALID_COMMAND_QUEUE] Error in step2 kernel finish' in short order (even after multiple driver/distro changes).
I have moved to mdcct (https://github.com/Mirkic7/mdcct) and started plotting successfully, however it indicates it will take 600 hours (25 days) to finish plotting my 64TB raid0 array.
I calculate that my raid array should be able to be fully written in around 9 hours in an ideal scenario so there is some serious CPU bottlenecking going on. Note: I am using a brand new i7 7700k cpu and am utilizing all 8 threads (all 8 virtual CPUs show as 100% usage).
I was wondering if it would be worthwhile to to mount my raid array as a network drive and use my Windows 10 gaming PC to crunch through the hashes.
Does anyone know roughly how much of an improvement I could expect to get from using a GPU plotter?
-
RE: Log into wallet from another computerposted in HowTo's & Tutorials
You also have to change the line
nxt.allowedUserHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
to
nxt.allowedUserHosts=*; localhost; [0:0:0:0:0:0:0:1];
-
RE: Log into wallet from another computerposted in HowTo's & Tutorials
Specifically you need to copy conf/nxt-default.properties to conf/nxt.properties and change the line nxt.apiServerHost=127.0.0.1 to nxt.apiServerHost=0.0.0.0
Then it is just a matter of configuring your iptables to open this port (lookup instructions for your distro).
Of course exposing your port to your local network will make your wallet far more vulnerable so do so at your own risk. It would be safer to only open this port when you need it.
-
RE: Log into wallet from another computerposted in HowTo's & Tutorials
Never mind, figured it out. Just had to add a new service to iptables and then edit the nxt.properties config file to allow access (changed 127.0.0.1 to 0.0.0.0 in a few places).
-
Log into wallet from another computerposted in HowTo's & Tutorials
I am working on setting up jminer and wallet to run on a headless Fedora server. Currently it is only possible to use the wallet from the computer that it is running on (the port is not exposed). Since there is no way to run a web browser on a headless server, I need to be able to access the wallet from another computer. Does anyone know an easy way to expose the wallet port on linux?
