patternfly / patternfly/react-topology
Spike: Investigate using web workers to enhance layout performance
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Describe the problem
Ansible topology uses force layout in a web worker to determine node positions prior to creating the model. It has been found to perform better than the force layout in PF topology.
Let's see if this can be used within a PF topology Layout and if it helps performance.
Expected output
A POC using a web worker based Layout with performance comparisons, or a reason why it cannot be done.
/cc @kialam
Jira Issue: PF-1999
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 comparing the Ansible topology force-layout web worker with the PF topology Layout described in the issue. Build a proof of concept and compare performance, or document why the approach cannot be used; completion is a measured comparison or a clear technical explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100