[Dynos] Smaller/Flexible Dyno Sizes
- Dominant language
- No language data
- Stars
- 225
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Providing smaller and more flexible dyno sizes was originally in-scope of the requirements of the recently launched Larger Dyno Sizes product release. It’s something we know our customers need and want for their apps on Heroku.
For techincal reasons, the new smaller types had to be separated from the larger dyno sizes release and we are continuing to prioritize researching the best way to offer these smaller tiers for our Heroku Customers.
We want to enable our customers to best meet their use cases and use Heroku resources as efficiently and elastically as possible.
We’ve had a large amount of feedback regarding smaller dyno sizes and have captured some of it below, but we’re looking forward to learning more.
Please let us know what use case and desired specifications you would be interested in using on Heroku.
Some examples from the Larger Dyno Size Roadmap item:
https://github.com/heroku/roadmap/issues/62#issuecomment-2024188489
https://github.com/heroku/roadmap/issues/62#issuecomment-1436114715
https://github.com/heroku/roadmap/issues/62#issuecomment-1269852943
https://github.com/heroku/roadmap/issues/62#issuecomment-1264992618
For additional context, we were targeting a Private-XS (extra small) dyno to add to our Private Spaces fleet with 512MB and 2 vCPUs. Feedback is welcome as well regarding that proposed specification.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.