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

Partition cell_outputs table #67

Closed
ShiningRay opened this issue Sep 21, 2022 · 4 comments
Closed

Partition cell_outputs table #67

ShiningRay opened this issue Sep 21, 2022 · 4 comments
Assignees
Labels
enhancement New feature or request refactor

Comments

@ShiningRay
Copy link
Contributor

ShiningRay commented Sep 21, 2022

The cell_outputs tables has more than 60,000,000 records.
The RDBMS usually has performance drop significantly after a table exceeds 20,000,000 records.
This is because the algorithm of B-Tree index, which has limit according to the layers in B-Tree.
So we can utilize the "partition" mechenism of RDBMS, to split big table into small partitions while not affecting the higher codes.

@ShiningRay ShiningRay added the enhancement New feature or request label Sep 21, 2022
@Keith-CY
Copy link
Member

By 11/09

@Keith-CY Keith-CY added this to the 2022/11/02 - 2022/11/09 milestone Nov 2, 2022
@Keith-CY
Copy link
Member

Blocked by migration of k8s

@Keith-CY
Copy link
Member

Waiting for support of @mdzh521

@ShiningRay
Copy link
Contributor Author

Suggested partition column:

  • cell status: active or dead (maybe pending when ckb_transactions and pool_transaction_entries are merged)
  • range(epoch) ( missing epoch column, add a epoch column )
  • range(block_number)
  • hash(transaction_id)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactor
Projects
Status: 🚩Pre Release
Status: Todo
Development

No branches or pull requests

5 participants