Verified
13 July 2026
Edis·1 vCPU · 1 GB RAM·Russia
Overall
39.9
/ 100
Scores
0–100 vs comparable servers
Ping
73.4/100
Speed
33.9/100
CPU
14.6/100
Memory
33.3/100
Disk
39.3/100
Category scores
Internet speed
Ping to control points
CPU performance
Memory bandwidth
Disk — random IOPS
Disk — sequential throughput
Disk latency (p95 / p99)
Network
| download_speed | 572.5 | Mbps |
| upload_speed | 407 | Mbps |
| ping_cloudflare | 11.224 | ms |
| ping_google | 4.339 | ms |
| ping_quad9 | 38.848 | ms |
| mtu | 1,500 |
Disk
| random_4k_read_iops | 34,176 | IOPS |
| random_4k_read_bw | 133.5 | MB/s |
| random_4k_read_lat_p95 | 1.761 | ms |
| random_4k_read_lat_p99 | 6.259 | ms |
| random_4k_write_iops | 18,508 | IOPS |
| random_4k_write_bw | 72.3 | MB/s |
| random_4k_write_lat_p95 | 5.079 | ms |
| random_4k_write_lat_p99 | 12.517 | ms |
| sequential_1m_read_iops | 5,227 | IOPS |
| sequential_1m_read_bw | 5,227.3 | MB/s |
| sequential_1m_read_lat_p95 | 3.359 | ms |
| sequential_1m_read_lat_p99 | 8.847 | ms |
| sequential_1m_write_iops | 769 | IOPS |
| sequential_1m_write_bw | 769.1 | MB/s |
| sequential_1m_write_lat_p95 | 10.027 | ms |
| sequential_1m_write_lat_p99 | 19.268 | ms |
CPU
| sysbench_single | 350.81 | events/s |
| sysbench_multi | 360.19 | events/s |
| gzip_compress | 126.2 | MB/s |
Memory
| memory_write_mb_s | 13,807.94 | MiB/s |
| memory_read_mb_s | 18,081.62 | MiB/s |
| OS | Ubuntu 22.04.5 LTS |
| Kernel | 5.15.0-173-generic |
| Virtualization | kvm |
| CPU model | Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz |
| vCPU | 1 |
| RAM (MB) | 957 |
| Disk (GB) | 14.36 |
| Agent | 1.1.0 |
| 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 →
Loading…
Could not load the data.
Plain-language summary
This report covers a real 1 vCPU · 1 GB RAM server at Edis in Russia (Saint Petersburg). Its clear strength is connectivity, scoring 58/100 with ping 4.3 ms, download 573 Mbps. If anything holds it back, it is the processor (360 events/s). For a VPN, tunnel or proxy this is a strong choice — those workloads live on the network, not the processor. The full breakdown, with every metric, is in the tabs above.