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

bench/db: update ft_transfers schema #11563

Merged
merged 14 commits into from
Jun 20, 2024
Merged

bench/db: update ft_transfers schema #11563

merged 14 commits into from
Jun 20, 2024

Conversation

mooori
Copy link
Contributor

@mooori mooori commented Jun 13, 2024

  • Adds a time_end field to allow recording both the start and end time of benchmark runs. This was requested in an issue which I couldn't find anymore in a quick search.
  • Values of total_transactions and size_state_bytes might get out of the integer range, hence the type of these columns is changed to bigint.

@mooori mooori changed the title bench/db bench/db: update ft_transfers schema Jun 13, 2024
@mooori mooori marked this pull request as ready for review June 13, 2024 10:21
@mooori mooori requested a review from a team as a code owner June 13, 2024 10:21
@@ -121,6 +121,7 @@ def commit_to_db(data: dict) -> None:
commit_hash, commit_time = get_commit()
response = {
"time": time_begin.strftime('%Y-%m-%dT%H:%M:%SZ'),
"time_end": datetime.now().strftime('%Y-%m-%dT%H:%M:%SZ'),
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@MCJOHN974 can you verify if this is the correct way to add time_end to the response?

Copy link
Member

Choose a reason for hiding this comment

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

Yes I think it will work

@mooori mooori requested a review from akashin June 13, 2024 14:59
Copy link

codecov bot commented Jun 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.47%. Comparing base (8189888) to head (784c78c).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #11563      +/-   ##
==========================================
- Coverage   71.48%   71.47%   -0.01%     
==========================================
  Files         788      788              
  Lines      160835   160835              
  Branches   160835   160835              
==========================================
- Hits       114968   114956      -12     
- Misses      40850    40863      +13     
+ Partials     5017     5016       -1     
Flag Coverage Δ
backward-compatibility 0.23% <ø> (ø)
db-migration 0.23% <ø> (ø)
genesis-check 1.36% <ø> (ø)
integration-tests 37.67% <ø> (-0.01%) ⬇️
linux 68.90% <ø> (+0.02%) ⬆️
linux-nightly 70.97% <ø> (-0.01%) ⬇️
macos 52.56% <ø> (-0.02%) ⬇️
pytests 1.59% <ø> (ø)
sanity-checks 1.38% <ø> (ø)
unittests 66.13% <ø> (-0.01%) ⬇️
upgradability 0.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@wacban wacban removed their request for review June 14, 2024 08:51
Copy link
Collaborator

@akashin akashin left a comment

Choose a reason for hiding this comment

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

Sorry, missed this!

@mooori
Copy link
Contributor Author

mooori commented Jun 20, 2024

@akashin, @MCJOHN974 could you please take another look, I've added a new migration as discussed on Zulip:

  • Naming a column user causes lint errors, so I went for initiator instead. Also added a context field to store more information about the benchmark run.
  • Technically these two columns would better be added in a separate PR, however that would make it more difficult to keep the script on the node in synch with the db schema. As the PR remains small, I think its acceptable to squeeze initiator, context in here.

@mooori mooori requested a review from akashin June 20, 2024 08:56
@mooori mooori requested a review from MCJOHN974 June 20, 2024 08:56
@mooori mooori added this pull request to the merge queue Jun 20, 2024
github-merge-queue bot pushed a commit that referenced this pull request Jun 20, 2024
- Adds a `time_end` field to allow recording both the start and end time
of benchmark runs. This was requested in an issue which I couldn't find
anymore in a quick search.
- Values of `total_transactions` and `size_state_bytes` might get out of
the `integer` range, hence the type of these columns is changed to
`bigint`.
@mooori mooori removed this pull request from the merge queue due to a manual request Jun 20, 2024
@mooori mooori added this pull request to the merge queue Jun 20, 2024
Merged via the queue into near:master with commit 10ca11a Jun 20, 2024
29 of 30 checks passed
@mooori mooori deleted the bench-db-types branch June 20, 2024 12:21
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.

None yet

3 participants