It's important to understand how much budget your allocation requires. You need to estimate your budget when requesting an allocation, but don't worry if you get it wrong, you can always request more later.
Here are 4 different methods to help you determine how much budget you need.
1. Recommended Budgets for Common use-cases.
If you are new to Nectar, the simplest approach may be to specify a "recommended" SU budget for corresponding to one of the following common use-cases:
"Like my laptop"
A typical researcher laptop has 4 cores and 8GB of RAM. That is equivalent to an instance with an m3.medium flavor. The SU cost for an m3.medium for one year is 1,000 SU.
"A bigger laptop"
A high end researcher laptop might have 8 cores and 16GB of RAM. That is equivalent to an instance with an m3.large flavor. The SU cost for an m3.large for one year is 2,000 SU.
"I just want to run a website"
A typical website to host some web pages, some small web applications, or some datasets needs 2 cores and 4GB of RAM. That is equivalent to an instance with an m3.small flavor. The SU cost for an m3.small for one year is 500 SU.
Use-case For Allocation
SU Budget Estimate
I want compute power like my laptop.
I want a bigger, more powerful laptop.
I just want to run a website.
2. Estimating based on Flavors.
If you have a good idea of what kind of Nectar resources you are likely to need, you can do your own estimate calculations based on the flavors.
- Look at the Nectar Flavors page and work out which one(s) best fit your needs.
- Take the SU cost per hour (or year) for a chosen flavor and multiply that by the time you intend to run the instance during the allocation period.
- Sum over all of the instances to get the total budget.
Example Flavor Calculation
SU Budget Estimate
2 x m3.large instance for 6 months
2 x 2,000 SU x 0.5 years
3. Estimating based on previous usage patterns.
If you have have been using compute resources (e.g. instances) on the Nectar Cloud for a while, you can view your project usage in the Dashboard.
- Check out the Usage Trend page to get an idea of how many service units your project has used over time.
- When the page loads, it will show you data for the past 3 months by default. You can change the date range to a more relevant period if you like.
- On this page you can see which instances were running, including the flavor, to help you understand the usage breakdown.
4. Same as last time.
If you're renewing an allocation, you could simply request the same budget that was approved in the last period. However, in this case it's a good idea to checkout the Allocation Usage page to make sure your previous budget was appropriate.