No.
Thanks, I've read announcement few minutes later once again - more carefully ![]()
For some reason I feel like a winner hahahaha. Crazy times.
No.
Thanks, I've read announcement few minutes later once again - more carefully ![]()
For some reason I feel like a winner hahahaha. Crazy times.
Hello,
What if I'm paying monthly for my machine and got 30 days cancelation period? Am I affected by price changes or it stays as it is now? I've created ticket, but maybe I can get answer a little faster here.
Best Regards
Same as Yours (if I'm not mistaken) - Vienna.
They definetly did some fixes or someone stopped killing it. This is not direct nvme, it's behind some network backend.
I performed it also on one of my other VPS machines (you know, "french one", since company name is forbidden here ![]()
fio --name=mixed_workload --filename=~/fio_test.file --size=10G \
--rw=randrw --rwmixread=75 --bs=4k --ioengine=libaio --direct=1 \
--numjobs=4 --iodepth=16 --runtime=60 --time_based --group_reporting
mixed_workload: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=16
...
fio-3.39
Starting 4 processes
mixed_workload: Laying out IO file (1 file / 10240MiB)
Jobs: 4 (f=4): [m(4)][100.0%][r=117MiB/s,w=39.3MiB/s][r=30.0k,w=10.1k IOPS][eta 00m:00s]
mixed_workload: (groupid=0, jobs=4): err= 0: pid=673285: Mon Aug 3 22:13:12 2026
read: IOPS=30.0k, BW=117MiB/s (123MB/s)(7043MiB/60004msec)
slat (usec): min=2, max=3946, avg=10.38, stdev= 9.88
clat (usec): min=134, max=51014, avg=2052.77, stdev=245.19
lat (usec): min=165, max=51033, avg=2063.16, stdev=245.40
clat percentiles (usec):
| 1.00th=[ 1516], 5.00th=[ 1811], 10.00th=[ 1893], 20.00th=[ 1975],
| 30.00th=[ 2008], 40.00th=[ 2040], 50.00th=[ 2073], 60.00th=[ 2089],
| 70.00th=[ 2114], 80.00th=[ 2147], 90.00th=[ 2180], 95.00th=[ 2245],
| 99.00th=[ 2409], 99.50th=[ 2606], 99.90th=[ 3720], 99.95th=[ 4424],
| 99.99th=[ 5932]
bw ( KiB/s): min=113270, max=144007, per=100.00%, avg=120335.01, stdev=672.90, samples=476
iops : min=28317, max=36001, avg=30083.66, stdev=168.21, samples=476
write: IOPS=10.1k, BW=39.3MiB/s (41.2MB/s)(2359MiB/60004msec); 0 zone resets
slat (usec): min=2, max=3972, avg=11.43, stdev=11.19
clat (usec): min=2, max=17159, avg=180.09, stdev=155.39
lat (usec): min=41, max=17182, avg=191.52, stdev=155.85
clat percentiles (usec):
| 1.00th=[ 55], 5.00th=[ 69], 10.00th=[ 79], 20.00th=[ 95],
| 30.00th=[ 110], 40.00th=[ 126], 50.00th=[ 143], 60.00th=[ 163],
| 70.00th=[ 192], 80.00th=[ 235], 90.00th=[ 314], 95.00th=[ 404],
| 99.00th=[ 701], 99.50th=[ 873], 99.90th=[ 1549], 99.95th=[ 2073],
| 99.99th=[ 3916]
bw ( KiB/s): min=36752, max=50000, per=100.00%, avg=40304.07, stdev=412.25, samples=476
iops : min= 9188, max=12500, avg=10075.93, stdev=103.05, samples=476
lat (usec) : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.12%, 100=5.81%
lat (usec) : 250=14.78%, 500=3.75%, 750=0.62%, 1000=0.21%
lat (msec) : 2=20.13%, 4=54.52%, 10=0.05%, 20=0.01%, 50=0.01%
lat (msec) : 100=0.01%
cpu : usr=5.14%, sys=13.44%, ctx=1376674, majf=0, minf=47
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=100.0%, 32=0.0%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.1%, 32=0.0%, 64=0.0%, >=64=0.0%
issued rwts: total=1803037,603923,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=16
Run status group 0 (all jobs):
READ: bw=117MiB/s (123MB/s), 117MiB/s-117MiB/s (123MB/s-123MB/s), io=7043MiB (7385MB), run=60004-60004msec
WRITE: bw=39.3MiB/s (41.2MB/s), 39.3MiB/s-39.3MiB/s (41.2MB/s-41.2MB/s), io=2359MiB (2474MB), run=60004-60004msec
Disk stats (read/write):
sda: ios=1802735/603988, sectors=14421952/4832152, merge=6/26, ticks=3676582/96701, in_queue=3773289, util=64.59%
Alles anzeigen
So i performed same fio as davorzec on my RS 2000 (iddling)
fio --name=mixed_workload --filename=~/fio_test.file --size=10G \
--rw=randrw --rwmixread=75 --bs=4k --ioengine=libaio --direct=1 \
--numjobs=4 --iodepth=16 --runtime=60 --time_based --group_reporting
mixed_workload: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=16
...
fio-3.39
Starting 4 processes
mixed_workload: Laying out IO file (1 file / 10240MiB)
Jobs: 4 (f=0): [f(4)][100.0%][r=284MiB/s,w=93.6MiB/s][r=72.7k,w=23.9k IOPS][eta 00m:00s]
mixed_workload: (groupid=0, jobs=4): err= 0: pid=500344: Mon Aug 3 21:52:35 2026
read: IOPS=75.1k, BW=293MiB/s (308MB/s)(17.2GiB/60001msec)
slat (nsec): min=761, max=1884.1k, avg=2652.56, stdev=1984.20
clat (usec): min=55, max=13371, avg=782.53, stdev=128.74
lat (usec): min=77, max=13377, avg=785.18, stdev=128.77
clat percentiles (usec):
| 1.00th=[ 474], 5.00th=[ 685], 10.00th=[ 709], 20.00th=[ 734],
| 30.00th=[ 758], 40.00th=[ 766], 50.00th=[ 783], 60.00th=[ 799],
| 70.00th=[ 816], 80.00th=[ 832], 90.00th=[ 857], 95.00th=[ 881],
| 99.00th=[ 938], 99.50th=[ 971], 99.90th=[ 1139], 99.95th=[ 1336],
| 99.99th=[ 6587]
bw ( KiB/s): min=280752, max=358266, per=100.00%, avg=300339.15, stdev=1602.27, samples=480
iops : min=70188, max=89566, avg=75084.82, stdev=400.56, samples=480
write: IOPS=25.1k, BW=98.0MiB/s (103MB/s)(5878MiB/60001msec); 0 zone resets
slat (nsec): min=912, max=525562, avg=2967.64, stdev=1934.44
clat (usec): min=35, max=18793, avg=196.68, stdev=139.03
lat (usec): min=39, max=18796, avg=199.65, stdev=139.03
clat percentiles (usec):
| 1.00th=[ 114], 5.00th=[ 127], 10.00th=[ 135], 20.00th=[ 147],
| 30.00th=[ 157], 40.00th=[ 167], 50.00th=[ 180], 60.00th=[ 190],
| 70.00th=[ 204], 80.00th=[ 221], 90.00th=[ 260], 95.00th=[ 330],
| 99.00th=[ 537], 99.50th=[ 635], 99.90th=[ 996], 99.95th=[ 1352],
| 99.99th=[ 6783]
bw ( KiB/s): min=92336, max=121717, per=100.00%, avg=100324.64, stdev=729.36, samples=480
iops : min=23084, max=30429, avg=25081.16, stdev=182.34, samples=480
lat (usec) : 50=0.01%, 100=0.06%, 250=22.27%, 500=3.17%, 750=20.00%
lat (usec) : 1000=54.24%
lat (msec) : 2=0.22%, 4=0.01%, 10=0.02%, 20=0.01%
cpu : usr=2.30%, sys=8.87%, ctx=4464948, majf=0, minf=46
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=100.0%, 32=0.0%, >=64=0.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.1%, 32=0.0%, 64=0.0%, >=64=0.0%
issued rwts: total=4505067,1504862,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=16
Run status group 0 (all jobs):
READ: bw=293MiB/s (308MB/s), 293MiB/s-293MiB/s (308MB/s-308MB/s), io=17.2GiB (18.5GB), run=60001-60001msec
WRITE: bw=98.0MiB/s (103MB/s), 98.0MiB/s-98.0MiB/s (103MB/s-103MB/s), io=5878MiB (6164MB), run=60001-60001msec
Disk stats (read/write):
vda: ios=4493392/1501032, sectors=35947560/12009064, merge=30/98, ticks=3513055/290992, in_queue=3804050, util=83.93%
Alles anzeigen
No, no e-mail response from support. Instability through whole weekend and today's average from my point of view performance (~5000 EPS in my app test while CPU stayed at ~1500 single core in geek benchmark) are somehow gone these evening.
https://browser.geekbench.com/v6/cpu/18901069 <- was
https://browser.geekbench.com/v6/cpu/18904577 <- currently
For a moment I thought I broke something and I'm still in shock and not sure wtf, but looks like not only CPU is fixed, but disk performance also increased. When last top result was ~12 seconds to perform operations, moment ago:
[18:58:29] Processed: 100000 | Δt: 0.42s | Total: 8.72s | AVG EPS: ~11471, LAP EPS: ~11927
[19:29:03] Processed: 100000 | Δt: 0.52s | Total: 10.67s | AVG EPS: ~9368, LAP EPS: ~9594
[19:38:20] Processed: 100000 | Δt: 0.51s | Total: 10.53s | AVG EPS: ~9499, LAP EPS: ~9812
These numbers are crazy good. Twice as good as earlier today. I doubt it stays like this forever ![]()
BTW
I will paste fio results in Your thread. I use different settings, but I will test ones you provided.
Well, I'm getting angry.
Did I rated my machine 8/10? Yes, based on this values (Time shifted -2h from Berlin time):
[23:32:16] Processed: 55000 | Δt: 0.69s | Total: 8.96s | AVG EPS: ~6140, LAP EPS: ~7215
[23:32:17] Processed: 60000 | Δt: 0.61s | Total: 9.57s | AVG EPS: ~6270, LAP EPS: ~8166
[23:32:17] Processed: 65000 | Δt: 0.62s | Total: 10.19s | AVG EPS: ~6382, LAP EPS: ~8119
[23:32:18] Processed: 70000 | Δt: 0.61s | Total: 10.80s | AVG EPS: ~6482, LAP EPS: ~8138
Total 100 000 message processed in 15.03s
currently its drowning again:
[11:12:19] Processed: 55000 | Δt: 1.38s | Total: 14.82s | AVG EPS: ~3712, LAP EPS: ~3623
[11:12:21] Processed: 60000 | Δt: 1.33s | Total: 16.15s | AVG EPS: ~3716, LAP EPS: ~3762
[11:12:22] Processed: 65000 | Δt: 1.27s | Total: 17.41s | AVG EPS: ~3733, LAP EPS: ~3952
[11:12:23] Processed: 70000 | Δt: 1.23s | Total: 18.64s | AVG EPS: ~3756, LAP EPS: ~4081
Total 100 000 message processed in 26.57s
These tests include cli php script talking to mariadb (read then write). Its like iddling for this kind of setup. I think storage is simply broken.
2026-08-01_13-39.png
I think netcup team should have a closer look at this, because such unstability is not acceptable.I bet it's faulty backend driver for storage.
Looks like You are right - they like to fix things silently. My machine is now performing ~8/10 and im fine with it comparing to my other machines in other company.
Dedicated cpu and ram BUT shared storage. Funny thing, because it's root of all problems with them. Some fio tests shows write latency tails exceeding much much above 100ms. Phenomenal was p99.99 = 6377ms latency spike.
Isn't this like playing video game with 200 FPS but with random screen stutters every few seconds? ![]()
Since few people here on forum got similar problems in this particular location I want to ask:
Did you checked all other factors? I've seen ST too, but not as huge as yours. Now its permanent 0 also. But unfortunatelly disk I/O is still random and CPU is not performing as it should 1258/6000 in geekbench 6 (original ~2200/11900). It's not as bad as it was earlier today or yestarday, but in my case, i still see random drops and spikes. Serioulsy i don't believe clocks are promised 3.7 Ghz per core. They seems to be default 2.3 for some reason or sometimes throttle.
I think it's main problem in my case also and it affects overall score. I opened ticket yesterday, because I 've made more test, including my own app which performance I know for sure. It's I/O bounded (database) and... oh boy, never saw results bad like this, maybe in debug mode.
I dont need much for my case, but stability is most important thing, thats why decided to RS line.
meanwhile. this is barely acceptable (7-7.5k events per second avg was inittially on this machine)
[09:46:27] Processed: 5000 | Δt: 1.57s | Total: 1.57s | AVG EPS: ~3192, LAP EPS: ~3192
[09:46:29] Processed: 10000 | Δt: 1.36s | Total: 2.93s | AVG EPS: ~3415, LAP EPS: ~3671
[09:46:30] Processed: 15000 | Δt: 1.22s | Total: 4.15s | AVG EPS: ~3612, LAP EPS: ~4085
[09:46:31] Processed: 20000 | Δt: 1.07s | Total: 5.22s | AVG EPS: ~3832, LAP EPS: ~4686
[09:46:32] Processed: 25000 | Δt: 0.97s | Total: 6.19s | AVG EPS: ~4038, LAP EPS: ~5146
[09:46:33] Processed: 30000 | Δt: 1.11s | Total: 7.31s | AVG EPS: ~4106, LAP EPS: ~4487
[09:46:34] Processed: 35000 | Δt: 1.24s | Total: 8.55s | AVG EPS: ~4094, LAP EPS: ~4020
[09:46:36] Processed: 40000 | Δt: 1.11s | Total: 9.66s | AVG EPS: ~4139, LAP EPS: ~4486
[09:46:37] Processed: 45000 | Δt: 1.07s | Total: 10.73s | AVG EPS: ~4193, LAP EPS: ~4683
[09:46:38] Processed: 50000 | Δt: 1.53s | Total: 12.26s | AVG EPS: ~4077, LAP EPS: ~3265
this is not acceptable
[09:56:11] Processed: 5000 | Δt: 2.03s | Total: 2.03s | AVG EPS: ~2469, LAP EPS: ~2469
[09:56:12] Processed: 10000 | Δt: 1.40s | Total: 3.42s | AVG EPS: ~2921, LAP EPS: ~3576
[09:56:14] Processed: 15000 | Δt: 1.43s | Total: 4.85s | AVG EPS: ~3093, LAP EPS: ~3507
[09:56:15] Processed: 20000 | Δt: 1.68s | Total: 6.53s | AVG EPS: ~3063, LAP EPS: ~2974
[09:56:17] Processed: 25000 | Δt: 1.86s | Total: 8.39s | AVG EPS: ~2978, LAP EPS: ~2683
[09:56:19] Processed: 30000 | Δt: 1.47s | Total: 9.87s | AVG EPS: ~3041, LAP EPS: ~3398
[09:56:20] Processed: 35000 | Δt: 1.48s | Total: 11.34s | AVG EPS: ~3086, LAP EPS: ~3386
[09:56:22] Processed: 40000 | Δt: 1.77s | Total: 13.12s | AVG EPS: ~3050, LAP EPS: ~2818
[09:56:24] Processed: 45000 | Δt: 2.10s | Total: 15.22s | AVG EPS: ~2957, LAP EPS: ~2379
[09:56:26] Processed: 50000 | Δt: 1.75s | Total: 16.97s | AVG EPS: ~2946, LAP EPS: ~2855
And this is... joke
[10:07:51] Processed: 5000 | Δt: 3.09s | Total: 3.09s | AVG EPS: ~1620, LAP EPS: ~1620
[10:07:54] Processed: 10000 | Δt: 2.79s | Total: 5.88s | AVG EPS: ~1701, LAP EPS: ~1791
[10:07:57] Processed: 15000 | Δt: 2.84s | Total: 8.72s | AVG EPS: ~1721, LAP EPS: ~1761
[10:08:00] Processed: 20000 | Δt: 3.22s | Total: 11.94s | AVG EPS: ~1675, LAP EPS: ~1553
[10:08:04] Processed: 25000 | Δt: 4.07s | Total: 16.00s | AVG EPS: ~1562, LAP EPS: ~1229
[10:08:07] Processed: 30000 | Δt: 3.29s | Total: 19.29s | AVG EPS: ~1555, LAP EPS: ~1522
[10:08:11] Processed: 35000 | Δt: 3.49s | Total: 22.78s | AVG EPS: ~1537, LAP EPS: ~1434
[10:08:14] Processed: 40000 | Δt: 3.17s | Total: 25.94s | AVG EPS: ~1542, LAP EPS: ~1579
[10:08:17] Processed: 45000 | Δt: 3.00s | Total: 28.95s | AVG EPS: ~1555, LAP EPS: ~1665
[10:08:20] Processed: 50000 | Δt: 2.89s | Total: 31.84s | AVG EPS: ~1570, LAP EPS: ~1729
Database mixed insert/updates from same dataset.
Hello,
I just put my hands on new RS 2000 yesterday evening. After initial configuration i started some benchmarks and I was very very happy with results. Over 2000 i single core an and almoust 12000 in multicore with 60k iops in 64K. wrk tests confirmed performance peaking at 32k RPS from caddy + frankenphp and symfony endpoints. I know, its raw test, not worth much in real life. However, good starting point to work with. Today, in peak hours my tests went down noticably, so i started yabs gb6 + fio and noticed massive drops to 1300+ SC and 7000 MC and disk fluctuate between 30 and 49k iops (average from few tests).
I'm not here to complain (yet hehe). I undertstand how it works, usually. But all this raised question about two things - first is CPU - since it is dedicated im my case, such a massive drop means CPU clock was probably reduced (ye, I don't believe 96 core chip can hold 3.7 Ghz boost from initial 2.3 all the time). Unfortunatelly cpu clock is not passed to VM, so I cant see it directly.
Disk operations I understand more, because I'm aware it's shared, but still dont know where is the baseline - what to expect?
I'll be glad if someone more expierienced share some thoughts on that. Maybe I just expect too much and can't swollow reality pill.