Update documentation
This commit is contained in:
parent
093dc907b3
commit
6d06bfb452
@ -16,6 +16,8 @@ The setup below is a minimal example for sealing 32 GiB sectors on Lotus:
|
|||||||
|
|
||||||
Note that 1GB sectors don't require as high of specs, but are likely to be removed as we improve the performance of 32GB sector sealing.
|
Note that 1GB sectors don't require as high of specs, but are likely to be removed as we improve the performance of 32GB sector sealing.
|
||||||
|
|
||||||
|
AMD CPU's are **highly recommended**, because of the `Intel SHA Extensions` instruction set that is available there since the `Zen` microarchitecture. Hence, AMD CPU's seem to perform much better on the testnet than other CPU's. Contrary to what the name implies, this extended instruction set is not available on recent Intel desktop/server chips.
|
||||||
|
|
||||||
## Testnet discoveries
|
## Testnet discoveries
|
||||||
|
|
||||||
- If you only have 128GiB of ram, enabling 256GB of **NVMe** swap on an SSD will help you avoid out-of-memory issues while mining.
|
- If you only have 128GiB of ram, enabling 256GB of **NVMe** swap on an SSD will help you avoid out-of-memory issues while mining.
|
||||||
|
@ -68,3 +68,14 @@ Worker 1, host othercomputer
|
|||||||
VMEM: [|||||||||||||| ] 23% 14 GiB/62.7 GiB
|
VMEM: [|||||||||||||| ] 23% 14 GiB/62.7 GiB
|
||||||
GPU: GeForce RTX 2080, not used
|
GPU: GeForce RTX 2080, not used
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Running locally for manually managing process priority
|
||||||
|
|
||||||
|
You can also run the **Lotus Seal Worker** on the same machine as your **Lotus Storage Miner**, so you can manually manage the process priority.
|
||||||
|
To do so you have to first **disable all seal task types** in the miner config. This is important to prevent conflicts between the two processes.
|
||||||
|
|
||||||
|
You can then run the storage miner on your local-loopback interface;
|
||||||
|
|
||||||
|
```sh
|
||||||
|
lotus-seal-worker run --address 127.0.0.1:2345
|
||||||
|
```
|
Loading…
Reference in New Issue
Block a user