Hello.... I've read tons of guides and watched youtube how to's.... I want my system to mine as efficiently as possible. If anyone could read over this and help me I would greatly appreciate it.
check_interval: 60
log_level: ERROR
check_interval: 60
datetime_format: "%Y-%m-%d %H:%M:%S"
include_seconds_for_phase: false
include_drive_info: true
include_cpu: true
include_ram: true
include_plot_stats: true
notifications:
# These are different settings in order to notified when the plot manager starts and when a plot has been completed.
# DISCORD
notify_discord: false
discord_webhook_url: https://discord.com/api/webhooks/0000000000000000/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
# IFTTT, ref https://ifttt.com/maker_webhooks, and this function will send title as value1 and message as value2.
notify_ifttt: false
ifttt_webhook_url: https://maker.ifttt.com/trigger/{event}/with/key/{api_key}
# PLAY AUDIO SOUND
notify_sound: false
song: audio.mp3
# PUSHOVER PUSH SERVICE
notify_pushover: false
pushover_user_key: xx
pushover_api_key: xx
# TELEGRAM
notify_telegram: false
telegram_token: xxxxx
# TWILIO
notify_twilio: false
twilio_account_sid: xxxxx
twilio_auth_token: xxxxx
twilio_from_phone: +1234657890
twilio_to_phone: +1234657890
instrumentation:
# This setting is here in case you wanted to enable instrumentation using Prometheus.
prometheus_enabled: false
prometheus_port: 9090
progress:
# phase_line_end: These are the settings that will be used to dictate when a phase ends in the progress bar. It is
# supposed to reflect the line at which the phase will end so the progress calculations can use that
# information with the existing log file to calculate a progress percent.
# phase_weight: These are the weight to assign to each phase in the progress calculations. Typically, Phase 1 and 3
# are the longest phases so they will hold more weight than the others.
phase1_line_end: 801
phase2_line_end: 834
phase3_line_end: 2474
phase4_line_end: 2620
phase1_weight: 33.4
phase2_weight: 20.43
phase3_weight: 42.29
phase4_weight: 3.88
global:
# These are the settings that will be used globally by the plot manager.
#
# max_concurrent: The maximum number of plots that your system can run. The manager will not kick off more than this
# number of plots total over time.
# max_for_phase_1: The maximum number of plots that your system can run in phase 1.
# minimum_minutes_between_jobs: The minimum number of minutes before starting a new plotting job, this prevents
# multiple jobs from starting at the exact same time. This will alleviate congestion
# on destination drive. Set to 0 to disable.
max_concurrent: 8
max_for_phase_1: 5
minimum_minutes_between_jobs: 7
jobs:
# These are the settings that will be used by each job. Please note you can have multiple jobs and each job should be
# in YAML format in order for it to be interpreted correctly. Almost all the values here will be passed into the
# Chia executable file.
#
# Check for more details on the Chia CLI here: https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference
#
# name: This is the name that you want to give to the job.
# max_plots: This is the maximum number of jobs to make in one run of the manager. Any restarts to manager will reset
# this variable. It is only here to help with short term plotting.
#
# [OPTIONAL] farmer_public_key: Your farmer public key. If none is provided, it will not pass in this variable to the
# chia executable which results in your default keys being used. This is only needed if
# you have chia set up on a machine that does not have your credentials.
# [OPTIONAL] pool_public_key: Your pool public key. Same information as the above.
#
# temporary_directory: Can be a single value or a list of values. This is where the plotting will take place. If you
# provide a list, it will cycle through each drive one by one.
# [OPTIONAL] temporary2_directory: Can be a single value or a list of values. This is an optional parameter to use in
# case you want to use the temporary2 directory functionality of Chia plotting.
# destination_directory: Can be a single value or a list of values. This is the final directory where the plot will be
# transferred once it is completed. If you provide a list, it will cycle through each drive
# one by one.
#
# size: This refers to the k size of the plot. You would type in something like 32, 33, 34, 35... in here.
# bitfield: This refers to whether you want to use bitfield or not in your plotting. Typically, you want to keep
# this as true.
# threads: This is the number of threads that will be assigned to the plotter. Only phase 1 uses more than 1 thread.
# buckets: The number of buckets to use. The default provided by Chia is 128.
# memory_buffer: The amount of memory you want to allocate to the process.
# max_concurrent: The maximum number of plots to have for this job at any given time.
# max_concurrent_with_start_early: The maximum number of plots to have for this job at any given time including
# phases that started early.
# initial_delay_minutes: This is the initial delay that is used when initiate the first job. It is only ever
# considered once. If you restart manager, it will still adhere to this value.
# stagger_minutes: The amount of minutes to wait before the next plot for this job can get kicked off. You can even set this to
# zero if you want your plots to get kicked off immediately when the concurrent limits allow for it.
# max_for_phase_1: The maximum number of plots on phase 1 for this job.
# concurrency_start_early_phase: The phase in which you want to start a plot early. It is recommended to use 4 for
# this field.
# concurrency_start_early_phase_delay: The maximum number of minutes to wait before a new plot gets kicked off when
# the start early phase has been detected.
# temporary2_destination_sync: This field will always submit the destination directory as the temporary2 directory.
# These two directories will be in sync so that they will always be submitted as the
# same value.
# exclude_final_directory: Whether to skip adding `destination_directory` to harvester for farming
# skip_full_destinations: When this is enabled it will calculate the sizes of all running plots and the future plot
# to determine if there is enough space left on the drive to start a job. If there is not,
# it will skip the destination and move onto the next one. Once all are full, it will
# disable the job.
# unix_process_priority: UNIX Only. This is the priority that plots will be given when they are spawned. UNIX values
# must be between -20 and 19. The higher the value, the lower the priority of the process.
# windows_process_priority: Windows Only. This is the priority that plots will be given when they are spawned.
# Windows values vary and should be set to one of the following values:
# - 16384 (BELOW_NORMAL_PRIORITY_CLASS)
# - 32 (NORMAL_PRIORITY_CLASS)
# - 32768 (ABOVE_NORMAL_PRIORITY_CLASS)
# - 128 (HIGH_PRIORITY_CLASS)
# - 256 (REALTIME_PRIORITY_CLASS)
# enable_cpu_affinity: Enable or disable cpu affinity for plot processes. Systems that plot and harvest may see
# improved harvester or node performance when excluding one or two threads for plotting process.
# cpu_affinity: List of cpu (or threads) to allocate for plot processes. The default example assumes you have
# a hyper-threaded 4 core CPU (8 logical cores). This config will restrict plot processes to use
# logical cores 0-5, leaving logical cores 6 and 7 for other processes (6 restricted, 2 free).
- name: MinerONE
max_plots: 999
farmer_public_key:
pool_public_key:
temporary_directory: Q:\Plotter
destination_directory: Z:\Plots
size: 32
bitfield: true
threads: 10
buckets: 128
memory_buffer: 4000
max_concurrent: 7
max_concurrent_with_start_early: 8
initial_delay_minutes: 0
stagger_minutes: 150
max_for_phase_1: 2
concurrency_start_early_phase: 7
concurrency_start_early_phase_delay: 0
temporary2_destination_sync: false
exclude_final_directory: false
skip_full_destinations: true
unix_process_priority: 10
windows_process_priority: 32
enable_cpu_affinity: false
cpu_affinity: [ 0, 1, 2, 3, 4, 5 ]
- name: MinerTHREE
max_plots: 999
farmer_public_key:
pool_public_key:
temporary_directory: L:\Plotter
destination_directory: F:\Plotsss
size: 32
bitfield: true
threads: 10
buckets: 128
memory_buffer: 4000
max_concurrent: 7
max_concurrent_with_start_early: 8
initial_delay_minutes: 0
stagger_minutes: 150
max_for_phase_1: 2
concurrency_start_early_phase: 7
concurrency_start_early_phase_delay: 0
temporary2_destination_sync: false
exclude_final_directory: false
skip_full_destinations: true
unix_process_priority: 10
windows_process_priority: 32
enable_cpu_affinity: false
cpu_affinity: [ 0, 1, 2, 3, 4, 5 ]
- name: MinerFOUR
max_plots: 999
farmer_public_key:
pool_public_key:
temporary_directory: Q:\
destination_directory: F:\
size: 32
bitfield: true
threads: 10
buckets: 128
memory_buffer: 4000
max_concurrent: 7
max_concurrent_with_start_early: 8
initial_delay_minutes: 0
stagger_minutes: 150
max_for_phase_1: 2
concurrency_start_early_phase: 7
concurrency_start_early_phase_delay: 0
temporary2_destination_sync: false
exclude_final_directory: false
skip_full_destinations: true
unix_process_priority: 10
windows_process_priority: 32
enable_cpu_affinity: false
cpu_affinity: [ 0, 1, 2, 3, 4, 5 ]
here is my pc rig
Operating System
Windows 10 Pro 64-bit
CPU
Intel Core i5 10400 @ 2.90GHz 57 °C
Comet Lake 14nm Technology
RAM
24.0GB Dual-Channel Unknown @ 1064MHz (15-15-15-36)
Motherboard
ASUSTeK COMPUTER INC. PRIME B460-PLUS (LGA1200) 27 °C
Graphics
SMS27A550H (1920x1080@59Hz)
4095MB NVIDIA GeForce RTX 3060 (Gigabyte) 29 °C
Storage
931GB Western Digital WDBRPG0010BNC-WRSN (Unknown (SSD))
119GB OCZ-VERTEX4 (SATA (SSD))
9313GB Western Digital WD Elements 25A3 USB Device (USB (SATA) ) 45 °C
931GB Crucial CT1000MX500SSD1 (SATA (SSD))
14902GB Western Digital WDC WD161KRYZ-01AGBB0 (SATA ) 32 °C
16764GB Seagate ST18000NM000J-2TV103 (SATA ) 29 °C
14902GB Western Digital WDC WD161KRYZ-01AGBB0 (SATA ) 30 °C
14902GB Western Digital WDC WD161KRYZ-01AGBB0 (SATA ) 31 °C
7452GB Seagate Desktop SCSI Disk Device (USB (SATA) ) 43 °C
13039GB Western Digital WD easystore 264D USB Device (USB (SATA) ) 47 °C
7452GB Seagate Desktop SCSI Disk Device (USB (SATA) )
Thank you , sorry for such the long msgStop watching youtube. Start reading forums and IT websites.
YouTubers have no clue about shit. They are only good at selling shit.
1 Like
yeah, thats why im here now
Start reading instead of begging for free help. You wanna make money with chia? Use your brain and start reading the existing knowledge.
Switching to madmax plotter usually easier now. Use wd black nvme as temp2 and a sata drive as temp1.
For your swar config, you have to first figure out how many plots at the same time your system can run. Ser that as global and divide that over the different drives/jobs.
Sata or usb ssd, really can only run one, maybe two plots at a time.
So you can try:
Global:
max_concurrent: 7
max_for_phase_1: 4
minimum_minutes_between_jobs: 10
- name: MinerONE
max_plots: 999
farmer_public_key:
pool_public_key:
temporary_directory: wdblack nvme
destination_directory: some hdd
size: 32
bitfield: true
threads: 6
buckets: 128
memory_buffer: 4000
max_concurrent: 3
max_concurrent_with_start_early: 4
initial_delay_minutes: 0
stagger_minutes: 120
max_for_phase_1: 2
concurrency_start_early_phase: 5
concurrency_start_early_phase_delay: 0
temporary2_destination_sync: false
exclude_final_directory: false
skip_full_destinations: true
windows_process_priority: 128
enable_cpu_affinity: false
cpu_affinity: [ 0, 1, 2, 3, 4, 5 ]
- name: MinerTWO (use same config for miner Three )
max_plots: 999
farmer_public_key:
pool_public_key:
temporary_directory: sata ssd
destination_directory: some hdd
size: 32
bitfield: true
threads: 6
buckets: 128
memory_buffer: 4000
max_concurrent: 2
max_concurrent_with_start_early: 2
initial_delay_minutes: 0
stagger_minutes: 0
max_for_phase_1: 1
concurrency_start_early_phase: 4
concurrency_start_early_phase_delay: 0
temporary2_destination_sync: false
exclude_final_directory: false
skip_full_destinations: true
windows_process_priority: 128
enable_cpu_affinity: false
cpu_affinity: [ 0, 1, 2, 3, 4, 5 ]
1 Like