Does running pruning node make the initial sync faster?

up vote
1
down vote

favorite

Does running bitcoind with -prune option make the initial blockchain sync faster or not? I know it makes it smaller on disk, but is it faster?

I keep reading conflicting information online - some state that it is quicker because you need less disk operations, some state it is about the same.

edited 15 mins ago

asked 22 mins ago

Karel BÃlek

1,10211341

add a commentÂ |Â

up vote
1
down vote

favorite

Does running bitcoind with -prune option make the initial blockchain sync faster or not? I know it makes it smaller on disk, but is it faster?

I keep reading conflicting information online - some state that it is quicker because you need less disk operations, some state it is about the same.

edited 15 mins ago

asked 22 mins ago

Karel BÃlek

1,10211341

add a commentÂ |Â

up vote
1
down vote

favorite

Does running bitcoind with -prune option make the initial blockchain sync faster or not? I know it makes it smaller on disk, but is it faster?

I keep reading conflicting information online - some state that it is quicker because you need less disk operations, some state it is about the same.

edited 15 mins ago

asked 22 mins ago

Karel BÃlek

1,10211341

Does running bitcoind with -prune option make the initial blockchain sync faster or not? I know it makes it smaller on disk, but is it faster?

I keep reading conflicting information online - some state that it is quicker because you need less disk operations, some state it is about the same.

bitcoind pruning

edited 15 mins ago

asked 22 mins ago

Karel BÃlek

1,10211341

edited 15 mins ago

asked 22 mins ago

Karel BÃlek

1,10211341

edited 15 mins ago

asked 22 mins ago

Karel BÃlek

1,10211341

asked 22 mins ago

Karel BÃlek

1,10211341

asked 22 mins ago

Karel BÃlek

1,10211341

add a commentÂ |Â

2 Answers
2

active

oldest

votes

up vote
2
down vote

accepted

No, pruning will not make the initial sync faster. The information that gets removed by pruning isn't accessed turning the initial sync.

Currently pruning makes the initial sync somewhat slower: more frequent flushes are performed in order to allow pruning to work, and the work of actually deleting things creates its own small slowdown. About the same is probably a fair statement in general.

answered 13 mins ago

G. Maxwell

1,322118

add a commentÂ |Â

up vote
1
down vote

Does running bitcoind with -prune option make the initial blockchain
sync faster or not?

No, it just allows you to define the maximum storage space for old blocks to use, but it will still download all of the blocks to verify them, deleting them afterwards.

-prune=<n>
 Reduce storage requirements by enabling pruning (deleting) of old
 blocks. This allows the pruneblockchain RPC to be called to
 delete specific blocks, and enables automatic pruning of old
 blocks if a target size in MiB is provided. This mode is
 incompatible with -txindex and -rescan. Warning: Reverting this
 setting requires re-downloading the entire blockchain. (default:
 0 = disable pruning blocks, 1 = allow manual pruning via RPC,
 >=550 = automatically prune block files to stay under the
 specified target size in MiB)

To reduce the sync time you could use the -assumevalid flag to move the default assumed valid block to an earlier block, but obviously this is a risk you take.

-assumevalid=<hex>
 If this block is in the chain assume that it and its ancestors are valid
 and potentially skip their script verification (0 to verify all,
 default:
 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0,
 testnet:
 0000000002e9e7b00e1f6dc5123a04aad68dd0f0968d8c7aa45f6640795c37b1)

answered 11 mins ago

JBaczuk

2,5291320

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "308"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f79591%2fdoes-running-pruning-node-make-the-initial-sync-faster%23new-answer', 'question_page');

);

Post as a guest

Name

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

up vote
2
down vote

accepted

No, pruning will not make the initial sync faster. The information that gets removed by pruning isn't accessed turning the initial sync.

answered 13 mins ago

G. Maxwell

1,322118

add a commentÂ |Â

up vote
2
down vote

accepted

No, pruning will not make the initial sync faster. The information that gets removed by pruning isn't accessed turning the initial sync.

answered 13 mins ago

G. Maxwell

1,322118

add a commentÂ |Â

up vote
2
down vote

accepted

No, pruning will not make the initial sync faster. The information that gets removed by pruning isn't accessed turning the initial sync.

answered 13 mins ago

G. Maxwell

1,322118

No, pruning will not make the initial sync faster. The information that gets removed by pruning isn't accessed turning the initial sync.

answered 13 mins ago

G. Maxwell

1,322118

answered 13 mins ago

G. Maxwell

1,322118

answered 13 mins ago

G. Maxwell

1,322118

answered 13 mins ago

G. Maxwell

1,322118

add a commentÂ |Â

up vote
1
down vote

Does running bitcoind with -prune option make the initial blockchain
sync faster or not?

No, it just allows you to define the maximum storage space for old blocks to use, but it will still download all of the blocks to verify them, deleting them afterwards.

-prune=<n>
 Reduce storage requirements by enabling pruning (deleting) of old
 blocks. This allows the pruneblockchain RPC to be called to
 delete specific blocks, and enables automatic pruning of old
 blocks if a target size in MiB is provided. This mode is
 incompatible with -txindex and -rescan. Warning: Reverting this
 setting requires re-downloading the entire blockchain. (default:
 0 = disable pruning blocks, 1 = allow manual pruning via RPC,
 >=550 = automatically prune block files to stay under the
 specified target size in MiB)

To reduce the sync time you could use the -assumevalid flag to move the default assumed valid block to an earlier block, but obviously this is a risk you take.

-assumevalid=<hex>
 If this block is in the chain assume that it and its ancestors are valid
 and potentially skip their script verification (0 to verify all,
 default:
 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0,
 testnet:
 0000000002e9e7b00e1f6dc5123a04aad68dd0f0968d8c7aa45f6640795c37b1)

answered 11 mins ago

JBaczuk

2,5291320

add a commentÂ |Â

up vote
1
down vote

Does running bitcoind with -prune option make the initial blockchain
sync faster or not?

No, it just allows you to define the maximum storage space for old blocks to use, but it will still download all of the blocks to verify them, deleting them afterwards.

-prune=<n>
 Reduce storage requirements by enabling pruning (deleting) of old
 blocks. This allows the pruneblockchain RPC to be called to
 delete specific blocks, and enables automatic pruning of old
 blocks if a target size in MiB is provided. This mode is
 incompatible with -txindex and -rescan. Warning: Reverting this
 setting requires re-downloading the entire blockchain. (default:
 0 = disable pruning blocks, 1 = allow manual pruning via RPC,
 >=550 = automatically prune block files to stay under the
 specified target size in MiB)

To reduce the sync time you could use the -assumevalid flag to move the default assumed valid block to an earlier block, but obviously this is a risk you take.

-assumevalid=<hex>
 If this block is in the chain assume that it and its ancestors are valid
 and potentially skip their script verification (0 to verify all,
 default:
 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0,
 testnet:
 0000000002e9e7b00e1f6dc5123a04aad68dd0f0968d8c7aa45f6640795c37b1)

answered 11 mins ago

JBaczuk

2,5291320

add a commentÂ |Â

up vote
1
down vote

Does running bitcoind with -prune option make the initial blockchain
sync faster or not?

No, it just allows you to define the maximum storage space for old blocks to use, but it will still download all of the blocks to verify them, deleting them afterwards.

-prune=<n>
 Reduce storage requirements by enabling pruning (deleting) of old
 blocks. This allows the pruneblockchain RPC to be called to
 delete specific blocks, and enables automatic pruning of old
 blocks if a target size in MiB is provided. This mode is
 incompatible with -txindex and -rescan. Warning: Reverting this
 setting requires re-downloading the entire blockchain. (default:
 0 = disable pruning blocks, 1 = allow manual pruning via RPC,
 >=550 = automatically prune block files to stay under the
 specified target size in MiB)

To reduce the sync time you could use the -assumevalid flag to move the default assumed valid block to an earlier block, but obviously this is a risk you take.

-assumevalid=<hex>
 If this block is in the chain assume that it and its ancestors are valid
 and potentially skip their script verification (0 to verify all,
 default:
 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0,
 testnet:
 0000000002e9e7b00e1f6dc5123a04aad68dd0f0968d8c7aa45f6640795c37b1)

answered 11 mins ago

JBaczuk

2,5291320

Does running bitcoind with -prune option make the initial blockchain
sync faster or not?

No, it just allows you to define the maximum storage space for old blocks to use, but it will still download all of the blocks to verify them, deleting them afterwards.

-prune=<n>
 Reduce storage requirements by enabling pruning (deleting) of old
 blocks. This allows the pruneblockchain RPC to be called to
 delete specific blocks, and enables automatic pruning of old
 blocks if a target size in MiB is provided. This mode is
 incompatible with -txindex and -rescan. Warning: Reverting this
 setting requires re-downloading the entire blockchain. (default:
 0 = disable pruning blocks, 1 = allow manual pruning via RPC,
 >=550 = automatically prune block files to stay under the
 specified target size in MiB)

To reduce the sync time you could use the -assumevalid flag to move the default assumed valid block to an earlier block, but obviously this is a risk you take.

-assumevalid=<hex>
 If this block is in the chain assume that it and its ancestors are valid
 and potentially skip their script verification (0 to verify all,
 default:
 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0,
 testnet:
 0000000002e9e7b00e1f6dc5123a04aad68dd0f0968d8c7aa45f6640795c37b1)

answered 11 mins ago

JBaczuk

2,5291320

answered 11 mins ago

JBaczuk

2,5291320

answered 11 mins ago

JBaczuk

2,5291320

answered 11 mins ago

JBaczuk

2,5291320

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

Search This Blog

Iyfjky