doc gen
This commit is contained in:
parent
dc247cc57d
commit
96ddd756f8
@ -380,11 +380,9 @@
|
|||||||
# A single partition may contain up to 2349 32GiB sectors, or 2300 64GiB sectors.
|
# A single partition may contain up to 2349 32GiB sectors, or 2300 64GiB sectors.
|
||||||
#
|
#
|
||||||
# The maximum number of sectors which can be proven in a single PoSt message is 25000 in network version 16, which
|
# The maximum number of sectors which can be proven in a single PoSt message is 25000 in network version 16, which
|
||||||
# means that a single message can prove at most 10 partinions
|
# means that a single message can prove at most 10 partitions
|
||||||
#
|
#
|
||||||
# In some cases when submitting PoSt messages which are recovering sectors, the default network limit may still be
|
# Note that setting this value lower may result in less efficient gas use - more messages will be sent,
|
||||||
# too high to fit in the block gas limit; In those cases it may be necessary to set this value to something lower
|
|
||||||
# than 10; Note that setting this value lower may result in less efficient gas use - more messages will be sent,
|
|
||||||
# to prove each deadline, resulting in more total gas use (but each message will have lower gas limit)
|
# to prove each deadline, resulting in more total gas use (but each message will have lower gas limit)
|
||||||
#
|
#
|
||||||
# Setting this value above the network limit has no effect
|
# Setting this value above the network limit has no effect
|
||||||
@ -403,6 +401,19 @@
|
|||||||
# env var: LOTUS_PROVING_MAXPARTITIONSPERRECOVERYMESSAGE
|
# env var: LOTUS_PROVING_MAXPARTITIONSPERRECOVERYMESSAGE
|
||||||
#MaxPartitionsPerRecoveryMessage = 0
|
#MaxPartitionsPerRecoveryMessage = 0
|
||||||
|
|
||||||
|
# Enable single partition per Post Message for partitions containing recovery sectors
|
||||||
|
#
|
||||||
|
# In cases when submitting PoSt messages which contain recovering sectors, the default network limit may still be
|
||||||
|
# too high to fit in the block gas limit. In those cases, it becomes useful to only house the single partition
|
||||||
|
# with recovery sectors in the post message
|
||||||
|
#
|
||||||
|
# Note that setting this value lower may result in less efficient gas use - more messages will be sent,
|
||||||
|
# to prove each deadline, resulting in more total gas use (but each message will have lower gas limit)
|
||||||
|
#
|
||||||
|
# type: bool
|
||||||
|
# env var: LOTUS_PROVING_SINGLERECOVERINGPARTITIONPERPOSTMESSAGE
|
||||||
|
#SingleRecoveringPartitionPerPostMessage = false
|
||||||
|
|
||||||
|
|
||||||
[Sealing]
|
[Sealing]
|
||||||
# Upper bound on how many sectors can be waiting for more deals to be packed in it before it begins sealing at any given time.
|
# Upper bound on how many sectors can be waiting for more deals to be packed in it before it begins sealing at any given time.
|
||||||
|
@ -698,11 +698,9 @@ After changing this option, confirm that the new value works in your setup by in
|
|||||||
A single partition may contain up to 2349 32GiB sectors, or 2300 64GiB sectors.
|
A single partition may contain up to 2349 32GiB sectors, or 2300 64GiB sectors.
|
||||||
|
|
||||||
The maximum number of sectors which can be proven in a single PoSt message is 25000 in network version 16, which
|
The maximum number of sectors which can be proven in a single PoSt message is 25000 in network version 16, which
|
||||||
means that a single message can prove at most 10 partinions
|
means that a single message can prove at most 10 partitions
|
||||||
|
|
||||||
In some cases when submitting PoSt messages which are recovering sectors, the default network limit may still be
|
Note that setting this value lower may result in less efficient gas use - more messages will be sent,
|
||||||
too high to fit in the block gas limit; In those cases it may be necessary to set this value to something lower
|
|
||||||
than 10; Note that setting this value lower may result in less efficient gas use - more messages will be sent,
|
|
||||||
to prove each deadline, resulting in more total gas use (but each message will have lower gas limit)
|
to prove each deadline, resulting in more total gas use (but each message will have lower gas limit)
|
||||||
|
|
||||||
Setting this value above the network limit has no effect`,
|
Setting this value above the network limit has no effect`,
|
||||||
@ -717,6 +715,19 @@ In those cases it may be necessary to set this value to something low (eg 1);
|
|||||||
Note that setting this value lower may result in less efficient gas use - more messages will be sent than needed,
|
Note that setting this value lower may result in less efficient gas use - more messages will be sent than needed,
|
||||||
resulting in more total gas use (but each message will have lower gas limit)`,
|
resulting in more total gas use (but each message will have lower gas limit)`,
|
||||||
},
|
},
|
||||||
|
{
|
||||||
|
Name: "SingleRecoveringPartitionPerPostMessage",
|
||||||
|
Type: "bool",
|
||||||
|
|
||||||
|
Comment: `Enable single partition per Post Message for partitions containing recovery sectors
|
||||||
|
|
||||||
|
In cases when submitting PoSt messages which contain recovering sectors, the default network limit may still be
|
||||||
|
too high to fit in the block gas limit. In those cases, it becomes useful to only house the single partition
|
||||||
|
with recovery sectors in the post message
|
||||||
|
|
||||||
|
Note that setting this value lower may result in less efficient gas use - more messages will be sent,
|
||||||
|
to prove each deadline, resulting in more total gas use (but each message will have lower gas limit)`,
|
||||||
|
},
|
||||||
},
|
},
|
||||||
"Pubsub": []DocField{
|
"Pubsub": []DocField{
|
||||||
{
|
{
|
||||||
|
Loading…
Reference in New Issue
Block a user