Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

delete sweatcoin testnet accounts from load tests #7888

Open
Tracked by #7634
jakmeier opened this issue Oct 20, 2022 · 2 comments
Open
Tracked by #7634

delete sweatcoin testnet accounts from load tests #7888

jakmeier opened this issue Oct 20, 2022 · 2 comments
Labels
T-integrations Team: issues relevant to the integrations team

Comments

@jakmeier
Copy link
Contributor

jakmeier commented Oct 20, 2022

Testnet state is getting large. Devs are running tests and never delete their data.

We are the worst offender here - each new sweatcoin testnet account for load test added millions of accounts, which translates to GBs of data.

Today on testnet, state sizes are:

Shard 0 Shard 1 Shard 2 Shard 3
6.8 GiB 4.7 GiB 48.3 GiB 43.6 GiB
  • shard 2 is where the lockup accounts are
  • shard 3 is wherethe token accounts are

we should

  • figure out which accounts take up how much space
  • see how easy it is to delete them (pretty sure delete account action will not work because state is too large)
  • delete accounts that we have keys, communicate with Sweatcoin asking them to delete their big testnet accounts
  • think about general solutions for accumulating big test state
@jakmeier
Copy link
Contributor Author

cc @firatNEAR, nothing urgent but something I just realized we should probably do

@firatNEAR firatNEAR added the T-integrations Team: issues relevant to the integrations team label Oct 20, 2022
@jakmeier
Copy link
Contributor Author

jakmeier commented May 1, 2023

@firatNEAR I assume the Sweatcoin tests haven't been cleaned up, yet?

cc @nikurt since you mentioned in a side comment of this epic state-parts analysis comment you want to look at why testnet contract state is so big.

My two cents: We don't know how much leftover state from Sweatcoin testing uses exactly. But we did create the full projected Sweatcoin state with 10M+ accounts on multiple near accounts. So I would expect something in the order of >10GB in terms of summed up TrieNodeWithSize::memory_usage and probably twice that in terms of disk usage.

@firatNEAR could maybe help with account names, if you actually want to dig deeper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-integrations Team: issues relevant to the integrations team
Projects
None yet
Development

No branches or pull requests

2 participants