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

Benchmarks #2655

Closed
wants to merge 2 commits into from
Closed

Benchmarks #2655

wants to merge 2 commits into from

Conversation

L-Qun
Copy link
Contributor

@L-Qun L-Qun commented Jul 13, 2024

Summary

I think benchmarks are really important; we also have a lot of them in the source code. However, we need a workflow to check every PR for any potential performance degradation.

image

Check List

  • pnpm run prettier for formatting code and docs

Copy link

vercel bot commented Jul 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
jotai ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 13, 2024 4:20pm

Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Copy link

LiveCodes Preview in LiveCodes

Latest commit: bb07658
Last updated: Jul 13, 2024 4:20pm (UTC)

Playground Link
React demo https://livecodes.io?x=id/DZRS9N2BJ

See documentations for usage instructions.

@L-Qun
Copy link
Contributor Author

L-Qun commented Jul 13, 2024

image

@dai-shi It seems we need to config the jotai repo, can you help to take a look at this issue?

@dai-shi
Copy link
Member

dai-shi commented Jul 14, 2024

Hi, thanks for your suggestion.

I agree that benchmarks are important, but the one we have now is very specific and doesn't cover real use cases. I don't see much benefit of adding a workflow with it.
That said, it would be nice if you create some benchmark suites. I actually think we can drop what we have now.

I don't think a workflow has a permission to write a comment from a forked repo. This happens with compressed-size-action.yml too. Anyway, the workflow isn't very important. The benchmark itself would be important.

@L-Qun
Copy link
Contributor Author

L-Qun commented Jul 14, 2024

Hi, thanks for your suggestion.

I agree that benchmarks are important, but the one we have now is very specific and doesn't cover real use cases. I don't see much benefit of adding a workflow with it. That said, it would be nice if you create some benchmark suites. I actually think we can drop what we have now.

I don't think a workflow has a permission to write a comment from a forked repo. This happens with compressed-size-action.yml too. Anyway, the workflow isn't very important. The benchmark itself would be important.

Got it thanks for your reply

@L-Qun L-Qun closed this Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants