This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Identify the default value for transaction account data size limit #28863
Comments
I think the default load-limit should allow creating one max-sized account. |
Yep, the default is currently allowing create an account with max size, as in this test (https://github.com/solana-labs/solana/blob/master/runtime/src/bank.rs#L18543-L18557). |
Ran modified ledger-tool on MB ledger, slot range [137375000, 137376339],
Taking out votes from sampled data,
|
2nd set of data from MB snapshots, slot range [136942999, 136943206]:
non-vote transactions have over 20MB data
|
3rd set of data from MB snapshot, slot range [166319750, 166320250]:
non-votge transactions have over 20MB data
|
identified 64MB as the limit that would not break anything in MNB right now. #29743 implemented it. Close this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
#27840 introduced a new compute-budget instruction to set max account data size limit per transaction, transactions try to load more than the limit will fail (https://github.com/solana-labs/solana/blob/master/docs/src/developing/programming-model/runtime.md#accounts-data-size-limit).
The default limit currently sets to 10MiB (defined here), which is the same as max account data size. This allows a transaction to load one max sized account without loading anything else.
The question is if this is sufficient?
Proposed Solution
Would like inputs.
The text was updated successfully, but these errors were encountered: