-
Notifications
You must be signed in to change notification settings - Fork 7
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
How to use your tool #3
Comments
The binary that you want to estimate the resource usage. See example. |
@mhausenblas if it helps, I've also found this tricky to use, cause usually it's not just a binary that you have, it would usually have a config associated with it, authentication associated with it and setting up its dependent services, etc. If this tool was to be used for setting kubernetes resource requests, it should consider an apiserver deployment under test, no? |
It's not Kubernetes specific and meant to be used from the CLI without any assumption about the setup/container orchestrator. |
I understand that your intention is to make the tool agnostic, but what I am saying from my experience that it's almost unusable for any real application deployed in Kubernetes (which is one of the orchestration platforms you're considering). |
Hi, I'd like to try your tool to estimate an appropriate pod limit and request but i don't get how to use it.
especially I do not understand what to input for the target.
what do you mean of $BINARY and $HTTP_URL_PATH here?
rsg --target $BINARY
[--api-path $HTTP_URL_PATH --api-port $HTTP_PORT --peak-delay $TIME_MS --sampletime-idle $TIME_SEC --sampletime-peak $TIME_SEC --export-findings $FILE --output json|openmetrics]
Example usage:
rsg --target test/test --api-path /ping --api-port 8080 2>/dev/null
The text was updated successfully, but these errors were encountered: