nextcloud / nextcloud/deck

Optimization and speed with lots of cards

Open
#5,259 11 comments 14 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement feature: boards feature: cards performance 🚀 technical debt
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Hello,

I migrated Trello cards with a Python script.

This migrated over 2400 cards, we've added a few hundred since then.
Some have been archived but the use of the DECK board is greatly slowed down, I have the impression that all the cards are still loaded even if they are archived.

I've deployed REDIS to optimize the overall performance of Nextcloud but it doesn't seem to have any effect on the DECK.

Looking forward to it,
Sincerely,

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 reproducing the slowdown with a Deck board containing more than 2,400 cards, including archived cards, and inspect how cards are loaded and filtered. Compare performance with and without archived cards present; done means identifying the loading bottleneck and demonstrating a measurable improvement in board responsiveness.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.