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.

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

Spike data storage mechanisms for client side performance #7769

Closed
woodenfurniture opened this issue Sep 18, 2024 · 3 comments
Closed

Spike data storage mechanisms for client side performance #7769

woodenfurniture opened this issue Sep 18, 2024 · 3 comments

Comments

@woodenfurniture
Copy link
Member

woodenfurniture commented Sep 18, 2024

Overview

App performance is bad and often the app requires a cache clear to bring performance back to acceptable level. Its likely our use of redux to store large amounts of data is the issue here, and use of a different approach could keep the app buttery smooth even in the present of relatively large volumes of data in the client.

References and additional details

.

Acceptance Criteria

Investigate possible solutions to avoiding use of redux for persistent data storage and access.

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

@woodenfurniture woodenfurniture changed the title placeholder - Spike data storage mechanisms for client side performance Spike data storage mechanisms for client side performance Sep 18, 2024
@0xean
Copy link
Contributor

0xean commented Sep 23, 2024

  • benchmark and identify the source of performance issues (initial hydration vs read/write at runtime)
  • document options in GH for conversation with team
  • report back to team after 1 days of research

@gomesalexandre
Copy link
Contributor

As discussed with @woodenfurniture, #7799 was the effective fix for the time being, but this spike still remains opened as a lower prio.

@0xean
Copy link
Contributor

0xean commented Oct 7, 2024

closing for now ... will reopen in ~4 weeks

@0xean 0xean closed this as completed Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants