-
Notifications
You must be signed in to change notification settings - Fork 280
No, the only aspect of plotman that considers free space is the archiving stage. Plotman currently assumes your ‘tmp’ and ‘dst’ drives will not become full. If you have configured multiple destination drives then plotman will try to balance these to avoid bottlenecks but it will not stop triggering new plots based on their amount of free space. Plotman is working on the assumption that you have archiving configured to ensure the dst drives are continually emptied or that you will manually free space.
The configuration is parsed when the plotman command is launched.
If you are running plotman interactive when you change the config file, you will have to press q to quit and re-run plotman interactive to reflect any changes.
Yes, press p to toggle active plot launching.
Other key commands are a to toggle archiving actions (if configured) and q to quit.
Nothing, the existing plotting processes will continue.
Plotman is NOT plotting itself, it is simply triggering background Chia Network or madMAx plotting processes and monitoring them via their log files.
If you quit plotman, no new jobs will be triggered but running ones will continue.
Plotman is stateless, i.e., if you restart it it will detect running jobs and continue following the settings in plotman.yaml.
No, neither the Chia Network plotter nor madMAx support this. Plotman's "suspend" function is only a thin wrapper around the general operating system process-suspend functionality. It is useful if you want to pause plotting processes (e.g., to clear up some disk space, temporarily reduce CPU or power consumption, etc.).
Plotman reports process state from the operating system via psutil process status. The process state has nothing to do with Plotman, but is a negotiation between the plotter process and your kernel.
| stat | psutil process status | Meaning |
|---|---|---|
| RUN | psutil.STATUS_RUNNING | Process is currently running |
| SLP | psutil.STATUS_SLEEPING | A process enters a Sleeping state when it needs resources that are not currently available. |
| DSK | psutil.STATUS_DISK_SLEEP | Process is waiting for read() or write() to/from a file descriptor return, process cannot be killed in this state |
| STP | psutil.STATUS_STOPPED | Process was suspended for example by using plotman suspend 0xplotid
|
The corresponding code can be found here: job.py
Empirically many people observe phase 1 of plotting to spend a lot of time in sleep state, so this appears to be normal, but we have not investigated enough to explain why.
The memory settings are passed through to the selected plotter program.
With the Chia Network plotter, the -b option sizes the sorting buffer.
The process requires additional memory to do other additional things, so total memory tends to be larger than the option you set.
If you are using the archive functionality, plotman will attempt to connect to your remote archive destination to get free-space statistics and to transfer files. For this to work, you need to set up ssh keys and rsyncd. Without those set up, you'll see errors.
Assuming you have installed Chia via the "git install" method, plotman should be run in the same directory that chia is installed to, generally that is chia-blockchain.
You should also activate the Python virtual environment before running plotman (source ./activate).
Your terminal window is too small to print all the info required by Plotman Interactive. Widen your terminal window or decrease the font size.