Timeweb·1 vCPU · 2 GB RAM·Netherlands
Network
| download_speed | 169 | Mbps |
| upload_speed | 149.6 | Mbps |
| ping_cloudflare | 4.237 | ms |
| ping_google | 1.217 | ms |
| ping_quad9 | 7.993 | ms |
| mtu | 1,500 |
Disk
| sequential_1m_read_iops | 6,147 | IOPS |
| sequential_1m_read_bw | 6,147.2 | MB/s |
| sequential_1m_read_lat_p95 | 1.548 | ms |
| sequential_1m_read_lat_p99 | 2.343 | ms |
CPU
| sysbench_single | 575.78 | events/s |
| sysbench_multi | 573.98 | events/s |
| gzip_compress | 201.3 | MB/s |
Memory
| memory_write_mb_s | 18,898.36 | MiB/s |
| memory_read_mb_s | 42,387.35 | MiB/s |
| OS | Ubuntu 26.04.1 LTS |
| Kernel | 7.0.0-38-generic |
| Virtualization | kvm |
| CPU model | AMD EPYC-Rome Processor |
| vCPU | 1 |
| RAM (MB) | 1895 |
| Disk (GB) | 27.95 |
| Agent | 1.1.1 |
| Scoring | 2026.07b |
Exactly what the agent returned from this server — before rounding, with nothing edited out. Every number above is computed from this. Open separately →
Timeweb (1 vCPU · 2 GB RAM) was measured in Amsterdam, Netherlands — the real numbers are below. The standout here is RAM bandwidth — 75/100, backed by 42,387 MiB/s. The weaker spot is CPU (574 events/s), so demanding CPU workloads are not its best fit. A solid database host: the disk and memory numbers are what relational engines depend on most. The full breakdown, with every metric, is in the tabs above.