[5.x]: Queue jobs with large job data payloads causes sluggish UI/browser performance when viewing Queue Manager
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
What happened?
Description
When using queue jobs with large Job data payloads this can cause the performance/UI of the Queue Manager within the Craft CMS interface to become sluggish.
While this is dependent on the queue job data, an example scenario, such as the Formie plugin from @engram-design, when dealing with submission payloads and integrations like Microsoft Dynamics 365 CRM, which have a large POST payload data size, this tends to be the key area where the performance is sluggish.
While this is Formie specific area, it can in theory be caused by any queue job from any plugin or module, so it is not exclusive.
This isn't a bug in the sense that something is broken, it is potentially a non-optimal scenario depending on the job data sent and then viewing this job in the queue manager, where the full job data is output, which is useful for debugging purposes, but can hurt the UI and performance and at worse cause a browser hang.
Steps to reproduce
- Send a queue job with a large job data payload, e.g. a big JSON payload.
- View the job in the queue manager
- Observe sluggish UI/browser performance due to parsing the job data
Expected behavior
UI/browser performance is not to be affected.
Actual behavior
Potentially sluggish performance with large job data payloads.
Craft CMS version
5.7.11
PHP version
8.3
Operating system and version
No response
Database type and version
MySQL
Image driver and version
No response
Installed plugins and versions
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
Start by reproducing the issue from the Queue Manager entry point with a queue job containing a large JSON payload, then identify where the full job data is rendered. Done means viewing such a job no longer causes sluggish UI or browser performance while retaining useful job details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100