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

Investigate whether param estimator is affected by whether it runs on HDD or SSD #3098

Closed
MaksymZavershynskyi opened this issue Aug 7, 2020 · 8 comments
Assignees
Labels
A-contract-runtime Area: contract compilation and execution, virtual machines, etc T-contract-runtime Team: issues relevant to the contract runtime team

Comments

@MaksymZavershynskyi
Copy link
Contributor

And if it is affected switch to specific SSD hardware.

@MaksymZavershynskyi MaksymZavershynskyi added the A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) label Aug 7, 2020
@bowenwang1996 bowenwang1996 added A-contract-runtime Area: contract compilation and execution, virtual machines, etc T-contract-runtime Team: issues relevant to the contract runtime team and removed A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) labels Jun 29, 2021
@bowenwang1996
Copy link
Collaborator

@olonho what is the status of this issue?

@stale
Copy link

stale bot commented Sep 27, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Sep 27, 2021
@bowenwang1996
Copy link
Collaborator

@matklad @olonho

@stale stale bot removed the S-stale label Sep 27, 2021
@stale
Copy link

stale bot commented Dec 27, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Dec 27, 2021
@bowenwang1996
Copy link
Collaborator

@matklad friendly ping :)

@stale stale bot removed the S-stale label Dec 28, 2021
@matklad matklad assigned jakmeier and unassigned olonho Jan 4, 2022
@stale
Copy link

stale bot commented Apr 4, 2022

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Apr 4, 2022
@jakmeier
Copy link
Contributor

jakmeier commented Apr 7, 2022

So far, we tried to run on SSDs, which I think is expected from validators. That should be a valid approach for estimation as far as I am concerned.
Still, I want to keep this issue open. Measuring the difference between SSD and HDD seems useful and not too much work. I just need to do it one day...

@akhi3030 akhi3030 removed the S-stale label Jul 8, 2022
@matklad
Copy link
Contributor

matklad commented Aug 31, 2022

@jakmeier I think we should just close this: I don't think we have realistic use-cases for HDD validators? Like, it would be fun to know, but I don't think much useful.

@matklad matklad closed this as completed Aug 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-contract-runtime Area: contract compilation and execution, virtual machines, etc T-contract-runtime Team: issues relevant to the contract runtime team
Projects
None yet
Development

No branches or pull requests

7 participants