Specifications of compute instances in Cloud-V
This document contains the specifications of the compute instances available for users to run builds in Cloud-V. The term "Compute Instance", can also be safely interchanged with the terms "Build Executor" and "Runner".
| Name | CI Name String | Architecture | ISA String | Cores | Memory | Compute Instance Type |
|---|---|---|---|---|---|---|
| N/A | J-x86-1 (or) J-QMU-1 | x86_64 | N/A | 4 | 8GiB | Hardware with application-level emulator |
| intel i7-6500U | J-TESTVM-1 | x86_64 | N/A | 4 | 8GiB | Hardware |
| Raspberry Pi 4 Model B | J-RASP4-1 | aarch64 | ARMv8-A | 4 | 4GiB | Hardware |
| QEMU System Linux | J-QMS-1 | riscv64 | See Ext 1 at bottom | 2 | 2GiB | QEMU System emulator |
| VisionFive 1 | J-VF1-1 | riscv64 | rv64imafdc | 2 | 8GiB | Hardware |
| VisionFive 1 | J-VF1-2 | riscv64 | rv64imafdc | 2 | 8GiB | Hardware |
| VisionFive 1 | J-VF1-3 | riscv64 | rv64imafdc | 2 | 8GiB | Hardware |
| VisionFive 2 | J-VF2-1 | riscv64 | rv64imafdc | 4 | 8GiB | Hardware |
| VisionFive 2 | J-VF2-2 | riscv64 | rv64imafdc | 4 | 8GiB | Hardware |
| VisionFive 2 | J-VF2-3 | riscv64 | rv64imafdc | 4 | 8GiB | Hardware |
| VisionFive 2 | J-VF2-4 | riscv64 | rv64imafdc | 4 | 8GiB | Hardware |
| VisionFive 2 | J-VF2-5 | riscv64 | rv64imafdc | 4 | 8GiB | Hardware |
| VisionFive 2 | J-VF2-6 | riscv64 | rv64imafdc | 4 | 8GiB | Hardware |
| HiFive Unleashed | J-HF-1 | riscv64 | rv64imafdc | 4 | 8GiB | Hardware |
| Banana Pi F3 | J-BPF3-1 | riscv64 | rv64imafdcv _sscofpmf_sstc _svpbmt_zicbom _zicboz_zicbop _zihintpause |
8 | 4GiB | Hardware |
| Banana Pi F3 | J-BPF3-2 | riscv64 | rv64imafdcv _sscofpmf_sstc _svpbmt_zicbom _zicboz_zicbop _zihintpause |
8 | 16GiB | Hardware |
| Banana Pi F3 | J-BPF3-3 | riscv64 | rv64imafdcv _sscofpmf_sstc _svpbmt_zicbom _zicboz_zicbop _zihintpause |
8 | 16GiB | Hardware |
| Banana Pi F3 | J-BPF3-4 | riscv64 | rv64imafdcv _sscofpmf_sstc _svpbmt_zicbom _zicboz_zicbop _zihintpause |
8 | 16GiB | Hardware |
| Banana Pi F3 | J-BPF3-5 | riscv64 | rv64imafdcv _sscofpmf_sstc _svpbmt_zicbom _zicboz_zicbop _zihintpause |
8 | 16GiB | Hardware |
| Milk-V Jupiter | J-JUPITER-1 | riscv64 | rv64imafdcv _sscofpmf _sstcc _svpbmt _zicbom _zicboz _zicbop _zihintpause |
8 | 16GiB | Hardware |
| Milk-V Pioneer Box | J-pioneer-1 | riscv64 | rv64imafdc _zicntr _zicsr _zifencei _zihpm _xtheadvector |
64 | 8GiB | Hardware |
Ext1: rv64imafdcvh_zicbom_zicboz_zicntr_zicond_zicsr_zifencei_zihintntl_zihintpause_zihpm_zacas_zfa_zfh
zfhmin_zba_zbb_zbc_zbkb_zbkc_zbkx_zbs_zknd_zkne_zknh_zkr_zkt_zksed
zksh_ztso_zvbb_zvbc_zvfh_zvfhmin_zvkb_zvkg_
zvkned_zvknha_zvknhb_zvksed_smaia_smstateen_ssaia_sscofpmf_sstc_svinval_svnapot_svpbmt
Note: The J-QMU-1 and J-x86-1 are one and the same runner. The purpose of creating two separate executors for same hardware is that J-x86-1 is supposed to be specifically for x86 architecture whereas J-QMU-1 is specifically for the users who want to cross compile source code for riscv64 architecture and then use qemu-usermode to execute them. Nevertheless, the tooling available for J-x86-1 can also be used for J-QMU-1