-
Notifications
You must be signed in to change notification settings - Fork 115
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
Add "cost" command to estimate costs based on the current configuration #34
Comments
Hi @mvayngrib. Thanks for the feedback. I hope your lambdas are burning! Yes these two feats will be very cool. Something that will make it a ton better. Would be good to have some free hands on this. Do you want to contribute? 🤔 |
@goncaloneves i'd love to contribute, but not sure i'll have time in the short term. In the meantime, i'll be enjoying the new responsiveness of my lambdas :) |
Cool, no worries 🙌 I will leave this here and is certainly something that will be done in the future. |
Just a quick note on this, I'm right now(today) - investigating cloudwatch metrics for this - also for intelligent warmup so it checks the number of concurrent executions on average for the particular time of day - I'll chuck notes in here later on :-) |
Rename is since the smart warming up feature will be tracked on #181 This should be achievable either hardcoding prices or using the SDK (https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Pricing.html#describeServices-property) |
Somewhat of an unrelated question - Just curious, how much does it cost exactly to keep it warm 24/7 for a month? Just a ballpark figure or rough estimate is ok. |
You can see the maths in the readme: https://github.com/juanjoDiaz/serverless-plugin-warmup#cost Let me know if something is unclear :) |
awesome plugin!
it would be cool to be able to get a cost estimate of the sum of the warmups scheduled, e.g. with
serverless warmup cost
idk, how much this would save, but log group pre-processing before a function call can save the need for a warmup call - process the latest log group, check the request id time, and then decide whether to issue warmup call
The text was updated successfully, but these errors were encountered: