learningequality / learningequality/studio
Determine partitioning strategy for content and file tables
Open
@rtibbles is already working on this.
Since Feb 15, 2022.
DEV: backend
DEV: content
TAG: performance
TAG: research
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Current behavior
As studio usage has grown, database tables have grown to a size that makes performance optimization very difficult. The size makes queries or joins against these large tables very slow and therefore user operations to feel slow.
Desired outcomes
- Determine a strategy for partitioning the
ContentNodeandFiledatabase tables:- How many buckets should we initially define for each?
- What's the best field to partition the
Filetable? - What's the best way to migrate to partitioned structures?
- Perform some manual testing if possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.