parse-community / parse-community/parse-dashboard
Slow performance on Large classes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
Issue Description
Clicking on a cell takes a few seconds to highlight
[Violation] 'readystatechange' handler took 292ms
[Violation] 'click' handler took 7485ms
[Violation] 'click' handler took 7778ms
Steps to reproduce
Select a class with many columns, inspect the console on chrome and click a few cells. There is also a performance hit when selecting a filter. This may be a rendering issue when drawing the cells of the table.
Environment
Dashboard
- Parse Dashboard version:
6.0.0 - Browser (Safari, Chrome, Firefox, Edge, etc.):
Chrome - Browser version:
130.0.6723.71 (Official Build) (x86_64)
Server
- Parse Server version:
7.3.0 - Operating system:
mac - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
local
Database
- System (MongoDB or Postgres):
MongoDB - Database version:
6.1.0 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
local
Logs
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.
Research direction
Reproduce the issue in Chrome by selecting a class with many columns, clicking cells, and selecting a filter while watching the browser console. The payload names no files, tests, or entry points; done means cell highlighting and filter selection no longer produce multi-second delays or the reported click-handler violations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100