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

Memory leak test for browser client #182

Closed
slvrtrn opened this issue Jul 13, 2023 · 1 comment
Closed

Memory leak test for browser client #182

slvrtrn opened this issue Jul 13, 2023 · 1 comment
Assignees
Labels
browser must-have required for the initial release
Milestone

Comments

@slvrtrn
Copy link
Contributor

slvrtrn commented Jul 13, 2023

We already have leak benchmarks for Node.js, which can also be repurposed for Browser.

@slvrtrn slvrtrn added the must-have required for the initial release label Jul 13, 2023
@slvrtrn slvrtrn added this to the 0.2.0-beta milestone Jul 13, 2023
@slvrtrn slvrtrn self-assigned this Jul 13, 2023
@slvrtrn
Copy link
Contributor Author

slvrtrn commented Jul 19, 2023

Works fine with React. For example, cell_towers streaming never exceeded 30M memory consumption and frequently dropped to <10M.

  1. npx create-react-app my-app
  2. Add this (using either of two functions for selects/inserts): https://gist.github.com/slvrtrn/4588013222038c48cc2ad4ea6159e15e
  3. Run and monitor memory consumption in the Chrome Memory tab

@slvrtrn slvrtrn closed this as completed Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser must-have required for the initial release
Projects
None yet
Development

No branches or pull requests

1 participant