1. Home
  2. Docs
  3. Yonohub
  4. Resources and Billing

Resources and Billing

Hardware resources are needed for many Yonohub actions, such as building an environment, running a job, running a YonoArc pipeline, etc. In order to meet the requirements of different workloads, Yonohub offers four resource models with different CPU, memory, SSD, and GPU resources as follows:

Resource ModelCPU CoresMemory (GB)SSD (GiB)GPU
C11430
C22850
C8832200
GK1656340Tesla K80
12 GB Memory

 

Whenever Yonohub needs to allocate hardware resources for an action, Yonohub allows you to select the resource model you wish. It is important to note that the resource model you select for a particular action does not limit your options for future actions. For example, you can build an environment using C1, but later use the same environment to start a custom app using C2.

 

Pricing information is detailed here. With Yonohub, you only pay as long as you are using the resource. Yonohub uses Per-Second Billing with a minimum of two minutes for each action.

 

You can track your current balance and your transactions as follows:

  1. Click your profile picture on the top-right corner of Yonohub’s main view.
  2. Click Account Settings.
  3. Click the Transactions History tab. Your current balance is shown at the top-right corner.
  4. Select the start and end dates, and click Filter
    • The Deposits table shows the history of your deposits including the amount and the date of each deposit
    • The Storage table shows the history of your storage transactions. Each month has a single transaction although storage billing is updated much more frequently. Your data in YonoDrive and the size of your YonoEBuilder environments affects these storage transactions.
    • The Resource Models table shows the details of your transactions including the Application, Resource Model, Start Time, End Time, Duration, and Cost of each transaction. A running transaction has a red circle beside its end time.

You can always use Express Build/Launch to allocate your resource model faster, but this incurs an additional 30% cost compared to the corresponding non-express resource model. If Yonohub wasn’t able to allocate your resource model fast enough, no additional cost will be incurred. Non-express build/launch are hidden by default, but you can show them by checking Enable normal launch from your Account Settings.