metabase / metabase/metabase

[Epic] Fix performance issues with personal collections

Open
#28,190 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

.Epic .Team/AdminWebapp
Dominant language
Clojure
Stars
49.3k
Forks
6.8k
Avg merge
1d 13h
Merged PRs (30d)
653

Description

Fixes https://github.com/metabase/metabase/issues/28068
Fixes https://github.com/metabase/metabase/issues/24330

### Milestone 1

As a quick fix, make the basic app flow work without loading all personal collections. You should be able to log into Metabase and view a saved question without loading all personal collections.

- [x] #28199
- [x] #28379
- [ ] FE - Load personal collections only where needed

### Milestone 2

Rework FE components that depend on `tree` endpoint to use `search` instead, with loading more items only when a collection is selected. It's a lot of work, so lets prioritize components that are used more often and should be easier to convert.

- [ ] FE - `ItemPicker`
- [ ] FE - `SavedQuestionPicker`
- [ ] FE - `MainNavBarContainer`
- [ ] FE - `DataSelector`
- [ ] FE - `DataPicker`
- [ ] FE - `CollectionPermissionsModal`

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the frontend components listed in the milestone—ItemPicker, SavedQuestionPicker, MainNavBarContainer, DataSelector, DataPicker, and CollectionPermissionsModal—and compare their use of the tree and search endpoints. Verify the login and saved-question flows without loading all personal collections, then confirm each prioritized component loads more items only when a collection is selected.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
frontend, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.