why does this sync action seem to not be resume-able?

[ofirgeller]

it take a long time and if I want to use my computer memory for something else it will stat from 0 next time I start the app.

[michalrus]

Hey @ofirgeller,

That percentage is not syncing, it's replaying what's already on your disk. Once you let it finish (especially after a cardano-node/Daedalus update), it should be more/less instantaneous the next time you run it.

The sync percentage (writing from the network to your disk) will pick up where you left it, though.

[ofirgeller]

Whatever the action is (syncing/ replying) it takes hours and if you stop it in the middle you have to start from zero, I understand that next time it will be fast, I am still asking why can't this stage be resume-able.

Cant you write the result to disk once in a while and pick up from there next time?

[michalrus]

@ofirgeller, it's not that simple unfortunately, but for a detailed explanation, please ask IntersectMBO/cardano-node. :)

[ofirgeller]

@michalrus I did not mean to suggest that it is "simple" or "easy", hope I did not offend. I was asking if it is possible and saying it think it has value.

can we maybe put it on some feature board along with the value it might have?

[michalrus]

Possibly, but Daedalus doesn't implement (and thus control) this behavior, we just use the Cardano node.

That's why I suggested moving this discussion to the IntersectMBO/cardano-node issue tracker. :)

[ofirgeller]

behavior is controlled by underlining project (cardano-node)

moved to:
IntersectMBO/cardano-node#5963