SWAR settings for 3900x/64GB RAM/2x2TB NVME

This page summarizes the projects mentioned and recommended in the original post on /r/chia

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • Swar-Chia-Plot-Manager

    This is a Cross-Platform Plot Manager for Chia Plotting that is simple, easy-to-use, and reliable.

  • Thank you! If you want, you can read more about this software here: https://github.com/swar/Swar-Chia-Plot-Manager

  • chia-blockchain

    Chia blockchain python implementation (full node, farmer, harvester, timelord, and wallet)

  • 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 tails 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: Only a single directory should be passed into here. This is where the plotting will take place. # [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. # stagger_minutes: The amount of minutes to wait before the next 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 seconds 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. - name: CUDA 001 max_plots: 7 farmer_public_key: pool_public_key: temporary_directory: D:\chiaTemp temporary2_directory: destination_directory: F:\chia size: 32 bitfield: true threads: 8 buckets: 128 memory_buffer: 4000 max_concurrent: 6 max_concurrent_with_start_early: 8 stagger_minutes: 28 max_for_phase_1: 2 concurrency_start_early_phase: 4 concurrency_start_early_phase_delay: 38 temporary2_destination_sync: false

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts