They resolved my issue this afternoon
Hope you get yours sorted too
Beiträge von PieR
-
-
I opened a ticket this afternoon and support excalated it to 2nd level.
-
I got same problem on the new RS2000 PRO vps:
The issue seems on the gateway NLB
ping 152.53.132.1
PING 152.53.132.1 (152.53.132.1) 56(84) bytes of data.
64 bytes from 152.53.132.1: icmp_seq=1 ttl=64 time=0.661 ms
64 bytes from 152.53.132.1: icmp_seq=2 ttl=64 time=0.607 ms
64 bytes from 152.53.132.1: icmp_seq=3 ttl=64 time=0.555 ms
64 bytes from 152.53.132.1: icmp_seq=3 ttl=64 time=0.888 ms (DUP!)
64 bytes from 152.53.132.1: icmp_seq=4 ttl=64 time=0.530 ms
64 bytes from 152.53.132.1: icmp_seq=5 ttl=64 time=4.32 ms
64 bytes from 152.53.132.1: icmp_seq=6 ttl=64 time=0.543 ms
64 bytes from 152.53.132.1: icmp_seq=6 ttl=64 time=0.577 ms (DUP!)
64 bytes from 152.53.132.1: icmp_seq=7 ttl=64 time=11.2 ms
64 bytes from 152.53.132.1: icmp_seq=8 ttl=64 time=1.53 ms
64 bytes from 152.53.132.1: icmp_seq=8 ttl=64 time=12.2 ms (DUP!)
64 bytes from 152.53.132.1: icmp_seq=9 ttl=64 time=4.31 ms
64 bytes from 152.53.132.1: icmp_seq=10 ttl=64 time=1.60 ms
64 bytes from 152.53.132.1: icmp_seq=10 ttl=64 time=12.6 ms (DUP!)
64 bytes from 152.53.132.1: icmp_seq=11 ttl=64 time=0.477 ms
64 bytes from 152.53.132.1: icmp_seq=11 ttl=64 time=12.4 ms (DUP!)
64 bytes from 152.53.132.1: icmp_seq=12 ttl=64 time=16.1 ms
64 bytes from 152.53.132.1: icmp_seq=13 ttl=64 time=0.531 ms
64 bytes from 152.53.132.1: icmp_seq=14 ttl=64 time=0.469 ms
64 bytes from 152.53.132.1: icmp_seq=15 ttl=64 time=0.544 ms
64 bytes from 152.53.132.1: icmp_seq=16 ttl=64 time=0.476 ms
64 bytes from 152.53.132.1: icmp_seq=16 ttl=64 time=0.502 ms (DUP!)
-
Check the "Settings" in your SCP
Oh! I didnt know of such an option !
Now I wonder what's setup is the "best"
thanks!
-
Comparing the
cat /proc/cpuinfocommand output from both machines, with the help of AI I found these potentially interesting insights:RS2000 PRO:
- 8 logical processors distributed across 8 separate physical sockets
- Single-core architecture (1 core per socket)
- No hyperthreading
- Basic security mitigations
- "Scale-out" approach with physical isolation
RS1000 ULTRA:
- 6 logical processors on a single physical socket
- Multi-core architecture (6 cores on one socket)
- Hyperthreading enabled
- Advanced security mitigations (ibrs_enhanced, flush_l1d)
- "Scale-up" approach with better inter-core communication
RS2000 PRO is configured as multiple separate sockets for isolation, while RS1000 ULTRA concentrates all cores on one powerful socket for better efficiency in inter-core communication.
I wonder how to RS2000 Ultra is configured and what benefits we can expect -
RS2000 Pro:
Confirmed, same as RS1000: AMD EPYC 9634 84-Core ProcessorSame disk speed as other RSs
Code
Alles anzeigen# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # # Yet-Another-Bench-Script # # v2025-04-20 # # https://github.com/masonr/yet-another-bench-script # # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # Di 29. Jul 14:17:30 CEST 2025 Basic System Information: --------------------------------- Uptime : 0 days, 4 hours, 8 minutes Processor : AMD EPYC 9634 84-Core Processor CPU cores : 8 @ 2246.624 MHz AES-NI : ✔ Enabled VM-x/AMD-V : ❌ Disabled RAM : 15.6 GiB Swap : 0.0 KiB Disk : 1007.9 GiB Distro : Debian GNU/Linux 12 (bookworm) Kernel : 6.1.0-37-amd64 VM Type : KVM IPv4/IPv6 : ✔ Online / ✔ Online IPv6 Network Information: --------------------------------- ISP : netcup GmbH ASN : AS197540 netcup GmbH Host : Netcup KVM VIE Location : Vienna, Vienna (9) Country : Austria fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda4): --------------------------------- Block Size | 4k (IOPS) | 64k (IOPS) ------ | --- ---- | ---- ---- Read | 168.56 MB/s (42.1k) | 342.89 MB/s (5.3k) Write | 169.00 MB/s (42.2k) | 344.69 MB/s (5.3k) Total | 337.56 MB/s (84.3k) | 687.59 MB/s (10.7k) | | Block Size | 512k (IOPS) | 1m (IOPS) ------ | --- ---- | ---- ---- Read | 347.48 MB/s (678) | 526.47 MB/s (514) Write | 365.95 MB/s (714) | 561.53 MB/s (548) Total | 713.43 MB/s (1.3k) | 1.08 GB/s (1.0k) iperf3 Network Speed Tests (IPv4): --------------------------------- Provider | Location (Link) | Send Speed | Recv Speed | Ping ----- | ----- | ---- | ---- | ---- Clouvider | London, UK (10G) | 2.68 Gbits/sec | busy | 23.8 ms Eranium | Amsterdam, NL (100G) | 2.71 Gbits/sec | busy | 11.7 ms Uztelecom | Tashkent, UZ (10G) | 2.33 Gbits/sec | 1.87 Gbits/sec | 84.5 ms Leaseweb | Singapore, SG (10G) | 811 Mbits/sec | 1.33 Gbits/sec | 157 ms Clouvider | Los Angeles, CA, US (10G) | 917 Mbits/sec | 684 Mbits/sec | 157 ms Leaseweb | NYC, NY, US (10G) | 2.35 Gbits/sec | 1.70 Gbits/sec | 102 ms Edgoo | Sao Paulo, BR (1G) | 1.06 Gbits/sec | 558 Mbits/sec | 204 ms iperf3 Network Speed Tests (IPv6): --------------------------------- Provider | Location (Link) | Send Speed | Recv Speed | Ping ----- | ----- | ---- | ---- | ---- Clouvider | London, UK (10G) | 2.65 Gbits/sec | 2.29 Gbits/sec | 23.8 ms Eranium | Amsterdam, NL (100G) | 2.69 Gbits/sec | 2.32 Gbits/sec | 11.6 ms Uztelecom | Tashkent, UZ (10G) | 2.47 Gbits/sec | 1.98 Gbits/sec | 84.5 ms Leaseweb | Singapore, SG (10G) | 2.17 Gbits/sec | 1.69 Gbits/sec | 157 ms Clouvider | Los Angeles, CA, US (10G) | 1.11 Gbits/sec | 446 Mbits/sec | 157 ms Leaseweb | NYC, NY, US (10G) | 1.92 Gbits/sec | 1.38 Gbits/sec | 103 ms Edgoo | Sao Paulo, BR (1G) | 2.17 Gbits/sec | 362 Mbits/sec | 203 ms Geekbench 6 Benchmark Test: --------------------------------- Test | Value | Single Core | 1904 Multi Core | 9840 Full Test | https://browser.geekbench.com/v6/cpu/13078278 YABS completed in 12 min 12 sec -
Rs2000 pro: I will let you know in a few minutes
