Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spike: Research performance implications of new web app polling behavior #2435

Open
exalate-issue-sync bot opened this issue Dec 4, 2024 · 0 comments
Open

Spike: Research performance implications of new web app polling behavior #2435

exalate-issue-sync bot opened this issue Dec 4, 2024 · 0 comments
Assignees
@toddlees

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Dec 4, 2024 •
edited
Loading

Research performance implications of new web app polling behavior.

Identify cpu / memory impacts as clients increase.

We should be able to test this by simply opening a number of clients at once and observing how the app metric respond. fecfile-web-app metrics

If metrics shift noticeably, create follow up ticket to remediate the impact. This will require working with BA/Design to determine responsiveness requirements for refresh. Related to https://fecgov.atlassian.net/browse/FECFILE-1842

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1876
@exalate-issue-sync exalate-issue-sync bot changed the title Spike: Research performance implications of new polling behavior Spike: Research performance implications of new web app polling behavior Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@toddlees toddlees

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@toddlees