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

[Feat] Add patching speed check #1148

Merged
merged 12 commits into from
Nov 16, 2024
Merged

[Feat] Add patching speed check #1148

merged 12 commits into from
Nov 16, 2024

Conversation

BrettCleary
Copy link
Collaborator

@BrettCleary BrettCleary commented Nov 8, 2024

Summary

Throw if patching will take longer than the download.

Using rough estimate numbers to get some estimates.

Log with "Patching Too Slow" instead of "Patching Error" so metrics graphs don't see it as a failed event.

  • Introduces a new patching error object to accomplish this

closes https://github.com/HyperPlay-Gaming/product-management/issues/755

@BrettCleary BrettCleary self-assigned this Nov 8, 2024
Comment on lines 1693 to 1695
// @TODO: get these speed values from local checks of download/write speed
const downloadSpeedInKBPerSecond = 25 * 1024
const extractionSpeedInKBPerSecond = 50 * 1024
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

open to suggestions here. I'd suggest we leave for another future iteration though

Comment on lines 1700 to 1701
// @TODO: get this value from local check of patching speed
const patchingSpeedEstimateInKBPerSecond = 5 * 1024
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

open to suggestions here as well. perhaps this could be the fallback value and we could attempt to get it from a LD flag?

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe add an object with these amounts and we can import them from LD.
This way we can alter any of them to make the calculation more precise.

@BrettCleary BrettCleary marked this pull request as ready for review November 9, 2024 20:28
@BrettCleary BrettCleary added the PR: Ready-For-Review PR is ready to be reviewed by peers label Nov 9, 2024
Copy link
Contributor

@jiyuu-jin jiyuu-jin left a comment

Choose a reason for hiding this comment

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

This looks great, testing now!

Copy link
Contributor

@flavioislima flavioislima left a comment

Choose a reason for hiding this comment

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

LGTM

@BrettCleary BrettCleary added PR: Ready-For-Test PR is ready to be tested by a QA and removed PR: Ready-For-Review PR is ready to be reviewed by peers labels Nov 15, 2024
Copy link

@nyghtstalker nyghtstalker left a comment

Choose a reason for hiding this comment

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

In order for the new patching to start I had to delete the old manifest version 0 so the client could download version 1. After, I was able to confirm the updated patching and noticed the improved speed.

image

@BrettCleary BrettCleary merged commit 2f302c2 into main Nov 16, 2024
9 checks passed
@BrettCleary BrettCleary deleted the feat/patch_speed_check branch November 16, 2024 00:09
@github-actions github-actions bot locked and limited conversation to collaborators Nov 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
PR: Ready-For-Test PR is ready to be tested by a QA
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants