t2a-standard-48 by Google Cloud Platform
(All-cores)
(Single-core)
Specifications
Server Metadata
Vendor ID | gcp |
Server ID | 1220007 |
Name | t2a-standard-48 |
Description | 48 vCPUs, 192 GB RAM |
Family | t2a |
Hw Virt | |
Average Time To Start | 15 |
Status | active |
Observed At | 2026-07-17T00:20:39.715689 |
Availability
| REGION / ID | SPOT | ONDEMAND |
|---|---|---|
Council Bluffs (US) / us-central1 | 0.7154 USD/h | 1.848 USD/h |
Eemshaven (NL) / europe-west4 | 1.0537 USD/h | 1.9413 USD/h |
Jurong West (SG) / asia-southeast1 | 0.681 USD/h | 2.279 USD/h |
Processor
vCPUs | 48 |
CPU Allocation | Dedicated |
CPU Cores | 48 |
CPU Speed | 3 GHz |
CPU Architecture | arm64 |
CPU Manufacturer | Ampere |
CPU Family | ARMv8 |
CPU Model | Neoverse-N1 |
CPU L1D Cache | 64 KiB |
CPU L1D Cache Total | 3 MiB |
CPU L1I Cache | 64 KiB |
CPU L1I Cache Total | 3 MiB |
CPU L2 Cache | 1 MiB |
CPU L2 Cache Total | 48 MiB |
CPU L3 Cache | 32 MiB |
CPU L3 Cache Total | 32 MiB |
CPU Flags | fp, asimd, evtstrm, aes, pmull, sha1, sha2, crc32, atomics, fphp, asimdhp, cpuid, asimdrdm, lrcpc, dcpop, asimddp, ssbs |
Ecpus | 48 |
Scalability | 100 |
System Resources and Accelerators
| MEMORY | |
|---|---|
Memory Amount | 192 GiB |
Memory Amount Actual | 192 GiB |
| GPU | |
|---|---|
GPU Count | 0 |
GPU Memory Min | 0 MiB |
GPU Memory Total | 0 MiB |
GPUs |
| STORAGE | |
|---|---|
Storage Size | 0 GB |
Storages |
| NETWORK | |
|---|---|
Inbound Traffic | 0 GB/month |
Outbound Traffic | 0 GB/month |
IPv4 | 0 |
CPU and System Topology
Server Description
An arm64-based instance featuring forty-eight dedicated cores and balanced memory, optimized for multi-threaded scale-out workloads and database operations.
Google Cloud Platform t2a-standard-48 is an arm64-based general-purpose instance featuring 48 dedicated physical cores on an Ampere Neoverse-N1 processor running at 3.0 GHz. It is configured with 192 GB of RAM, representing a balanced 4.0 GB per core ratio, with no local storage or GPU resources. Performance benchmarks reveal a contrast between weak single-core metrics, such as a Geekbench single-core score of 1110.0, and strong multi-core capabilities, highlighted by a stress-ng multi-core score of 87,022.37. Memory bandwidth and static web serving throughput remain average, while Redis SET operations perform strongly at 61.65 million operations per second. Due to weak single-threaded performance and poor text generation speeds on LLM models, this instance is best suited for multi-threaded, scale-out workloads like database operations, software compilation, and web serving.
Economics
Performance
Memory Bandwidth
Compression
OpenSSL
Geekbench Single-Core
Geekbench Multi-Core
Passmark CPU Scores
| BENCHMARK | SCORE |
|---|---|
Mark | 27399 |
Compression | 272501 |
Encryption | 7763 |
Extended Instructions | 35712 |
Floating Point Maths | 171834 |
Integer Maths | 226357 |
Physics | 3497 |
Prime Numbers | 214 |
Single Threaded | 1323 |
String Sorting | 156336 |
Passmark Memory Scores
| BENCHMARK | SCORE |
|---|---|
Memory Mark | 1963 |
Database Operations | 20474 |
Memory Latency | 70 |
Memory Read Cached | 11296 |
Memory Read Uncached | 8597 |
Memory Write | 14944 |
Stress-ng Raw Scores
Stress-ng Relative Multicore Performance
LLM Inference Speed for Prompt Processing
LLM Inference Speed for Text Generation
Static Web Server
Redis
Alternatives
Servers of the Same Family
| INSTANCE | vCPUs | MEMORY | GPUs |
|---|---|---|---|
| t2a-standard-1 | 1 | 4 GiB | 0 |
| t2a-standard-2 | 2 | 8 GiB | 0 |
| t2a-standard-4 | 4 | 16 GiB | 0 |
| t2a-standard-8 | 8 | 32 GiB | 0 |
| t2a-standard-16 | 16 | 64 GiB | 0 |
| t2a-standard-32 | 32 | 128 GiB | 0 |
Similar Servers
| INSTANCE | VENDOR | vCPUs | MEMORY | GPUs |
|---|