Category

Docker

Optimizing Your Chia Farming Operation: A Guide to Using Chia Farming Scripts for GPU Plotting and Efficient Plot Management

By | Chia, Docker, NVIDIA | No Comments

Chia farming has become increasingly popular as people look for ways to earn rewards by utilizing their computer’s processing power. While Chia farming can be a lucrative endeavor, it also requires a lot of disk space and can be a time-consuming process. Fortunately, these Chia farming scripts can help you optimize your plotting process, farm your plots, and move them efficiently, making your Chia farming operation more streamlined and potentially more profitable.

https://github.com/88plug/chia-farming
https://github.com/88plug/chia-farming

The first step in the Chia farming process is to prepare your hard drives. The prepare-drives.sh script can help you automate this process by formatting your specified drives with an ext4 file system, setting reserve space to 0%, disabling write-cache, and optimizing read-ahead caching for performance. This can help you save time and ensure that your hard drives are optimized for Chia farming.

Once your hard drives are prepared, you can start creating Bladebit plots. The Bladebit algorithm is faster than the CPU-based plotting algorithms and doesn’t require CUDA. The bladebit-plotting.sh script runs a Docker container that is configured with the necessary environment variables to create Bladebit plots efficiently. With Bladebit plots, you can potentially earn more rewards and speed up your Chia farming operation.

If you have a compatible GPU, you can create C7 Bladebit plots with the bladebit-cuda-plotting.sh script. This script uses the bladebit_cuda command-line tool to create plots with your GPU. The plots are generated with a plot count of 50000 and a thread count of 16. With C7 plots, you can further accelerate your Chia farming and potentially earn more rewards.

Once you’ve created your Bladebit CUDA plots, you’ll need to farm them to earn rewards. The harvester-compose.yml file provides a convenient way to configure a Docker container to farm your Bladebit CUDA plots. The file specifies a service named chia_harvester that runs a Docker container based on the cryptoandcoffee/chia-node-cuda:1 image. The container is configured to run as a harvester, and it connects to your farmer using the specified farmer_address and farmer_port. The container also specifies the location of the CA folder from your farmer, which is mounted as a volume inside the container. This allows the container to access your Bladebit CUDA plots, which are stored in the /plots directory.

Efficiently moving your plots is also important when it comes to Chia farming. The plot-mover.sh script can help you do this by using a list of farming drives and shuffling it to find an available drive. If a drive is available, the script checks for new plot files in the specified source directory and moves the first available plot file to the farming drive. The script can handle multiple transfers simultaneously and waits for a few seconds before checking for new plot files or available drives again. This can help you manage your Chia farming operation and keep your plots organized.

In addition to these scripts, there are other things you can do to optimize your Chia farming operation. For example, you may want to consider using a RAM disk to speed up the plotting process or using a network-attached storage (NAS) device to store your plots. You can also use tools like Chia Plot Manager to manage and monitor your plots.

It’s important to keep in mind that Chia farming can require a lot of disk space, and it may take some time before you start seeing rewards. However, with the help of these scripts and other optimization techniques, you can potentially earn more rewards and make your Chia farming operation more efficient. Just be sure to use these scripts carefully and only run them on drives that are dedicated to Chia farming.

In conclusion, Chia farming can be a rewarding activity if done correctly. By using these Chia farming scripts and other optimization techniques

Change Docker Default Location

By | Docker | No Comments

The most recent method to change the default data directory location is edit
[raw]
/lib/systemd/system/docker.service
[/raw]

Replace the ExecStart value with the following:
[raw]
ExecStart=/usr/bin/dockerd –graph=”/mnt/blockstorage/” -H fd://
[/raw]

Replace graph=”” with the location of your new storage.

or

Edit [raw]/etc/docker/daemon.json[/raw]

[raw]
{
“graph”: “/mnt/blockstorage”
}
[/raw]