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

gas and storage benchmarks #341

Merged
merged 10 commits into from
Feb 14, 2023
Merged

gas and storage benchmarks #341

merged 10 commits into from
Feb 14, 2023

Conversation

ailisp
Copy link
Member

@ailisp ailisp commented Feb 7, 2023

Add benchmark, readme and tips to benchmark your use case.

@ailisp ailisp marked this pull request as ready for review February 10, 2023 05:25
Copy link
Collaborator

@volovyks volovyks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great overall! My main concern is that it's better to store benchmark results in separate autogenerated files. It will allow us to update them with time, since gas usage will be constantly changing. But that can be done later, not a blocker now.

@@ -2,3 +2,4 @@ packages:
- "examples"
- "tests"
- "packages/*"
- "bench"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit

@@ -2,3 +2,4 @@ packages:
- "examples"
- "tests"
- "packages/*"
- "bench"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Bench" gives me wrong associations. Maybe "benchmark" is better?

import { near } from "near-sdk-js";

export function empty() {
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • lots of new empty lines at the end of files

@ailisp ailisp merged commit 343a062 into develop Feb 14, 2023
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