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

Consider increasing performance test suite coverage #4649

Open
tomduncalf opened this issue Jun 15, 2022 · 1 comment
Open

Consider increasing performance test suite coverage #4649

tomduncalf opened this issue Jun 15, 2022 · 1 comment

Comments

@tomduncalf
Copy link
Contributor

tomduncalf commented Jun 15, 2022 •
edited by sync-by-unito bot
Loading

Our current performance test suite only measures the performance of property access. It was suggested in #4443 (comment) that it would be useful to have performance benchmarks for writing, syncing, etc.
@tomduncalf
Copy link
Contributor Author

  • Property writes could be interesting because of e.g. type conversion
  • Index access into collections
  • Running existing tests on CI would be a good improvement (depends on having a predictable/stable environment to run tests against)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomduncalf