SpaceFarmers.io Wiki

User Tools

Site Tools

You are here: SpaceFarmers Wiki » guides » Complete plotting Guide » Virtual Plots
guides:plotting:virtualplots

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
guides:plotting:virtualplots [2024/02/07 16:39] – vleesbanaanguides:plotting:virtualplots [2024/02/07 17:59] – 172.68.50.79
Line 2: Line 2:
 Although k-32 is by far the [[https://dashboard.chia.net/d/CL1X4UWnk/blockchain-state?orgId=1&viewPanel=41|most used k-size]], chia allows us to plot big-k plots. As the number of proofs is directly proportional to the plot size in bytes, there is limited incentives on the revenue side to using larger k-plots. On the cost side however, using big k-plots offers a small advantage in terms of HDD power-saving. A k-32 has double the disk reads per byte and is accessed by the plot-filter twice more than a k-33, and four times for than a k-34, and 16 times more than a k-36, etc. One problem in leveraging these benefits has been that in order to fill up a drive to make best use of the capacity, a mixed bag of multi-k plots is required (see image below), resulting in a cost-saving that is insignificant enough to warrant a replot for most.  Although k-32 is by far the [[https://dashboard.chia.net/d/CL1X4UWnk/blockchain-state?orgId=1&viewPanel=41|most used k-size]], chia allows us to plot big-k plots. As the number of proofs is directly proportional to the plot size in bytes, there is limited incentives on the revenue side to using larger k-plots. On the cost side however, using big k-plots offers a small advantage in terms of HDD power-saving. A k-32 has double the disk reads per byte and is accessed by the plot-filter twice more than a k-33, and four times for than a k-34, and 16 times more than a k-36, etc. One problem in leveraging these benefits has been that in order to fill up a drive to make best use of the capacity, a mixed bag of multi-k plots is required (see image below), resulting in a cost-saving that is insignificant enough to warrant a replot for most. 
  
-|  Drive Size  |  Plotmix  |  Available GB  |  Chiapos Space  |  GB Free  |+|  Drive Capacity  |  Plotmix  |  Available GB  |  Total ChiaPos GB  |  GB Free  |
 |  5TB  |  35,37  |  4655.82  |  4615.43  |  40.39  | |  5TB  |  35,37  |  4655.82  |  4615.43  |  40.39  |
 |  8TB  |  32,33,34,35,36,37  |  7449.96  |  7182.09  |  267.86  | |  8TB  |  32,33,34,35,36,37  |  7449.96  |  7182.09  |  267.86  |
Line 13: Line 13:
 This means that any HDD using this method is accessed only ~18 (9216/512) times per day with the current plot filter. This allows us to put HDDs into standby_z (spin-down) or idle_c (reduce rpm), saving 80% and 50% respectively compared to drives filled with only C0 k-32s. This means that any HDD using this method is accessed only ~18 (9216/512) times per day with the current plot filter. This allows us to put HDDs into standby_z (spin-down) or idle_c (reduce rpm), saving 80% and 50% respectively compared to drives filled with only C0 k-32s.
  
-Whenever a signage point arrives, you need to check the plot filter for plots passing. This plot filter check is done purely against the plotID, and is done in memory/cached, so you don't need any disk io for it. When a plot passes the plot filter, you'll need to look up qualities from the plot, and that's when the disk io starts. With the current plot filter, a single plot is expected to pass only once every 512 signature points, or once every 80 minutes. +Whenever a signage point arrives, the harvester process checks the plot filter for plots passing. This plot filter check is done purely against the plotID, and is done in memory/cached, so no disk io is needed for it. When a plot passes the plot filter, the harvester will look up qualities from the plot, and that's when the disk io starts. With the current plot filter, a single plot is expected to pass only once every 512 signature points, or once every 80 minutes. 
 This means that if you have an 18TB drive filled with 165 k-32s, you have 165 different plotIDs per disk and you'll have a plot passing every 30 seconds or so requiring disk io. The disk will not be able to sleep. If, however, you have a single plotID per disk, your disk will only have to wake once every 80 minutes. It can sleep the rest of the time, which is much more power efficient. This means that if you have an 18TB drive filled with 165 k-32s, you have 165 different plotIDs per disk and you'll have a plot passing every 30 seconds or so requiring disk io. The disk will not be able to sleep. If, however, you have a single plotID per disk, your disk will only have to wake once every 80 minutes. It can sleep the rest of the time, which is much more power efficient.
  
Line 31: Line 31:
 But it also allows for more complex methods, such as using idle_c during winter, while switching to standby_z in summer to reduce electricity used for AC.  But it also allows for more complex methods, such as using idle_c during winter, while switching to standby_z in summer to reduce electricity used for AC. 
 Admittedly, the plotting requirements make this method prohibitive to many.  Admittedly, the plotting requirements make this method prohibitive to many. 
 +
 It is in recognition of the large variety of farmers that we try to bring attention to this method.  It is in recognition of the large variety of farmers that we try to bring attention to this method. 
  
guides/plotting/virtualplots.txt · Last modified: 2024/02/09 06:55 by vleesbanaan
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki