Skip to content

Conversation

Kartiiyer12
Copy link
Collaborator

@Kartiiyer12 Kartiiyer12 commented Sep 9, 2025

  • 10 minute interval for pruning is too aggressive and it causes very high I/O when syncing. Increasing it to 1 hour.
    Rationale -

    • Constant insert/delete cycles on address_utxo table
    • Index Maintenance: Heavy I/O from index rebuilds after 264M deletions
    • Write-Heavy Workload: 15:1 write-to-read ratio overwhelming storage
  • configure option for pruning batch size. Default is 3000 but if needed can be changed upto 10000 for faster deletion but it should not cause too much I/O while syncing

  • debug option for utxo store

@matiwinnetou matiwinnetou changed the title increase pruning interval chore: increase pruning interval Sep 10, 2025
@matiwinnetou matiwinnetou changed the title chore: increase pruning interval feat: increase pruning interval Sep 10, 2025
@matiwinnetou matiwinnetou changed the title feat: increase pruning interval fix: increase pruning interval Sep 10, 2025
store.utxo.pruning-interval=600
store.utxo.pruning-interval=3600
store.utxo.pruning-batch-size=${REMOVE_SPENT_UTXOS_BATCH_SIZE:3000}
logging.level.com.bloxbean.cardano.yaci.store=${LOG:error}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That should not be necessary actually, confusing. I wouldn't do this, it should take root logger

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The LOG env variable is the already existing. The logging was just added as we were not seeing the Yaci-indexer pruning logs and it needed to be turned to debug to see the logs. Could you clarify, is LOG env variable not root logging option?

Copy link
Collaborator

@matiwinnetou matiwinnetou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants