New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I think because of this thread, he was ragebaiting π
https://lowendtalk.com/discussion/comment/4870381#Comment_4870381
he offered refund, what else do you want?
An apology, of course!
As others have mentioned, the benchmark results still look usable depending on what you're using it for. At the end of the day, it's still a VPS. Resources are shared so performance can and will vary depending on what other users are doing at the time, and occasionally you are going to get noisy neighbors.
guys he's Vietnamese, and how yall accept to pay for 8 cores 9950X just to get 1100 multi core marks π
Is it just me, or was that not a very honest and to the point answer from the provider?
They simply state facts and tell it like it is, they do not try to cover it up or come with excuses. They admit the node is loaded and they can not fix it right now and therefor they offer a refund. I would without hesitation accept that answer and live with half-decent performance until they get the opportunity to upgrade. After all, this is a vps, it is all shared resources so half-decent performance is what you should expect.
I do not have any vps with @DigitalFyre but this thread makes me want to get some, an honest provider is hard to find these days. This was probably not what op intended but he just gave them a new customer.
yea i mean my eyes glaze at the ai phrasing and i get the op being annoyed at the situation but seemed like it was handled more than appropriately. different folks i guess.
I appreciate the honesty shown in your ticket acknowledging the issue, but the practice of overselling to the point of overloading raises serious questions about business ethics?!. While I understand that performance might drop compared to when I first purchased the service (when the server had fewer clients), the current level of degradation is unacceptable.
Naturally, I will be moving my business elsewhere, as there are plenty of good providers out there.
Please note that I am not a new customerβI have been with you since the initial launchβso this kind of profit-driven overcrowding is particularly disappointing.
Ok, good luck
Great idea when they can't be bothered to respond to tickets and just use AI )
Well, if the response is correct and answers my question I do not care who writes it.
And they claim to check each answer even if it's written by AI, so saying that they "can't be bothered to respond to tickets" is not really a fair judgement.
Customer service is one of those areas where I do not mind correctly implemented AI, since the average AI is usually more intelligent then the average customer. Not trying to offend anyone, but after 30 years in IT my expectation on the average customer is unfortunately extremely low not to say non-existent.
With price 10$ for 8c8g. I dont think you can expect extreme fast 8c with 8g ram at all on a 16/32 cpu. Ram is expensive u know
okay nvm, the commitment must be 4:1 to compensate this π
Enjoy your 8 vcore 9950x getting 1.1k in gb6 then, buy more from dogshit providers like this.
The unacceptable degradation is completely understandable, and we acknowledged it and offered a refund. As stated, right now, there's not much we can do except see what we can do about reasonable global throttling on disk and CPU use due to the number of VMs on the node. For what it's worth, this node has fewer than 60 VMs. Of course, even with cancellations, we will keep the location marked as OOS and won't deploy any additional services on that node.
I'm sorry to see you go, but it's also completely understandable. I refunded your most recent invoice (September, 2026), and you are not obligated to pay your outstanding invoice if you're moving your service to another provider. Please reach out to our team if you need additional time to migrate so I can disable automatic service suspension to help you migrate without any additional stress.
That's true that you have been a customer since our first LET offer. Thank you for the time you've spent with us and for using our services.
I truly wish there were something more impactful I could do about Singapore, and we have been working hard to secure more hardware in the region. Sadly, our efforts have been unsuccessful so far.
Plenty of repeated questions, although answered in the Knowledge Base, are still being asked. This is where automated responses from the AI assistant come in handy.
Also, I'd like to reiterate that the AI responses are still being reviewed by support staff, more often than not, by me. If there's a mistake or inaccuracy, we correct it and communicate the correction to the customer.
I support using AI to a certain degree. However, I'm not comfortable relying on it fully. We even have a banner in the AI Assistant chat that states, "AI can make mistakes. Please check important information.".
Last I checked, 48gb ECC is around ~$2k per stick.
OP received both
Literally looking into this right now
@DigitalFyre , sorry to ask this. But can you tell me the drives inside that hypervisor?
Assume usable space is 1800GB. His share is 60GB. Ratio, 30:1
While FIO at 4k it's 260.K:18.6K. So, 14:1
Perhaps the disks are capable of delivering more than 558K iops at 4k?
In Singapore, they are Nytro 5550M SSD 3.2TB XP3200LE70035 Gen4 NVMe. I have a "spare" disk on the node, so I could move some VMs to it. It might help with IO, but honestly, we need more hardware, and the first thing is to offload a good chunk of users from the old HV to the new one instead of going with some bandaid solution π€
Hmmm
Say usable space is 3000GB -> 1:50
OP should have receive 190/50= 3.8K iops. But he received 9.8k iops.
Maybe you should sell the spare disk/capacity to OP for additional $50/month π
OP should have receive 190/50= 3.8K iops. But he received 9.8k iops.
Maybe you should sell the spare disk/capacity to OP for additional $50/month π
π Nah! I wouldn't do that! Honestly, if you look at the node's load with a little less than 60 VMs, over the past 4 weeks, it's not unreasonable, and the RAM use is expected since we commit memory to users' VMs:
Node YABS:
FIO for the VM storage drive, not so great:
So OP definitely has a valid point regarding disk performance.
However, none of this matters as much as the fact that we still need to deploy additional hardware and lighten the load on this node.
What I can, and will, do is move some VMs over to the other drive and monitor the performance.
3$/Mo and some are pissed it is a bit oversold/cramed?
dafq
@rpqu , so normal capped speeds for NVME should be 3.8K IOPS, we have that on HDD, I think we need to revise the storage specs 
OK! I tested this out and moved a VM from the crowded disk to the other one. Things are most certainly significantly better.
With that said, I'll reach out to the customers who had disk performance issues and offer to move their VMs to help them get better performance. Also, I think I may have located a couple of I/O Hogs, whom I'll reach out to after throttling is applied.
Again, this is not a permanent fix. It's something to keep the node in a decent state until we procure more hardware.
On paper, yes. The guaranteed IO is 3.8K IOPS at 4k per 60GB on that drive. Is my calculation wrong?
not a customer but i appreciate your attitude, very classy.
...Yet
Thank you very much!
I would also like to thank everyone else in the thread who kept the discussion constructive and classy, and refrained from jumping to conclusions and using unsavory language.
I am still working on that node to figure out what really is causing the slowness.
I found conclusive data showing the disk is perfectly healthy and has virtually no wear. However, after writing a very large amount of data (887 TB) over its life, the drive's internal housekeeping appears to have fallen behind. ( I don't know how else to describe it )
One user had 600 million write requests and 1.2 billion read requests within a 50-day span on a 20 GB disk.
That said, I will take a moment to admit that the initial diagnostics and the quick assumption that it's just because there are a lot of VMs don't live up to the standards we hold ourselves to.
I'll keep doing what I need to do and schedule a maintenance window to do some housekeeping.
I'm real impressed with the way DigitalFyre has handled this thread.
That person should be throttled lol. 12M write request per day, 500K per hour. 138iops. Wtf this guy doing