Skip to content

Aggressive test for huge disk database stretches coming from epochs #634

Open
@TheQuantumPhysicist

Description

@TheQuantumPhysicist

Say an epoch is 5 days. An epoch should represent the close-to-empirical maximum of disk space we will need to write at once, in one database transaction.

If target block time is two minutes, we'll have around 720 blocks per day. In 5 days, that will be 3600 blocks.

If the maximum block size is 1 MB, then we should be prepared to write 3600 MB = 3.6 GB in one database transaction, which is really huge.

This problem should be studied thoroughly and tested against whatever database backend we choose to use. Especially lmdb, since it has a database resize procedure.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lmdbEverything related to lmdb key-value storestorageEverything related to storage, whether it's blockchain, wallet or otherwise

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions