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 mostly see them on Nodeseek nowadays. They buy servers in the US and sell VPSes to MJJs.
They recently created a LET thread which made me not really trust them anymore:
https://lowendtalk.com/discussion/211808/god-bless-you-never-need-to-order-services-from-gorillaservers/p1
edit: I found I had a brief conversation with them on LET and they seemed helpful. However I can't really say if the same goes for quality their services.
They had migration of their vps from one node to other in Frankfurt which is not very good atm. Before migration vm was great, now is so slow. Mby they are still working or something else.. lets give it a few days.
Yesterday, my hardware monitoring reflected that a node in Germany might have data hidden trouble, because I found that the I/O performance of this node was appalling, so I moved to another node urgently to avoid visible data disaster.
I don't quite understand what you mean by "not as fast as before"
If you feel slow in any operation, you may hit my CPU resource scheduling rule, resulting in your CPU performance being only 10% of the previous one, which will be automatically released within 24 hours.
You can check yourself if you want. Ticket #3831456
Like i said.. lets give it few days. However big + is communication, mail was sent before and after migration, ty for that
Hello:
I have reviewed your support ticket and confirmed that you are currently under CPU resource restrictions (performance capped at 10% of the standard level).
Under these conditions, all your system performance metrics will be significantly lower than before. However, this restriction will be lifted within 24 hours, provided you do not continue to trigger the CPU resource limit policy.
This policy is implemented to ensure fair resource usage for all users based on their purchased plans, rather than as a punitive restriction.
Additionally, it is worth noting that the previous hypervisor had write-back caching enabled, while the new hypervisor does not. The old hypervisor used SATA SSD RAID10, whereas the new one uses NVMe SSD RAID10.
How come, the vm was idle after migration ? Not single task on it. So this tells me running yabs ill be under CPU resource restrictions right ? . Thanks
I have also noticed that approximately 10 users experienced CPU throttling on their VMs following the migration. I have now lifted these restrictions for all affected accounts, including yours. You may now re-run your tests.
I am currently testing a new CPU credit system designed to promote fair resource usage. This system will be implemented only after we confirm that it accommodates the daily requirements of the vast majority of our users.
Probably yabs in same time ? That can happen alot here in let. We are exited for new configs and what to test it.. However thank you for lifting, hope your cpu credit system will work good for all users.