Poor performance after migrating to Linode

Hey @ks_007. Sorry you're having a bad experience. I found your ticket, we'll see if there's anything else we can recommend or do on our end that might change or improve your performance.

I found your ticket, we'll see if there's anything else we can recommend or do on our end that might change or improve your performance.This is not it. In my two days with Linode I'm having multiple issues. One is with the DNS and another one is with poor performance during peak hours.

Same code base and same configs (few basic ones) works fine in GCP, AWS and Digitalocean.

How does it make sense for Linode to say that there could be something wrong with my configuration.

I've had similar issue with Linode in the past, when I've moved one of my old node to a new one.
It turned out to be a "noisy neghbor", and Linode moved my vps to another server. ever since it works ok

But in my case they have denied the presence of a noisy neighbor. I'm in their new datacenter which is at Mumbai. Not sure if that is a reason. But Linode keeps insisting that there is something wrong with my configuration but not sure why my application runs well everywhere else and has a problem only in Linode.

@ks_007 I've reviewed your tickets and I'd like to apologize for any feelings you may have of being brushed off or unacknowledged. Generally speaking, if we suspect that an internal configuration issue as at the root of any performance issues, we'll focus there for troubleshooting efforts. While you're only seeing performance issues on our platform and not others, it doesn't rule out internal configuration problems (there are several potential issues when migrating applications as I'm sure you're well aware). Even so, if you're not assured that we have exhaustively checked for problems on our end and ruled them out as contributing to the issues you're experiencing, we're not providing the level of support we should be.

Since we're already working with you in Support tickets, it's best to resume troubleshooting there. Having said that, it would assist greatly if you could provide a picture of what your Linode's performance is looking like. In particular, outputs of commands like iostat 1 10 and MTR reports during times you're noticing performance problems will assist us greatly in pinpointing problems in our systems.

Otherwise, we're going to take a close look at all of your Linodes to rule out host issues like noisy neighbors as potential contributors to the issues you're seeing. Feel free to reach back out with any questions or concerns in the meantime.

The comment from the @bbigger was a bit late. We had suffered with this problem for two days (Thursday, Friday).

We had also moved our DNS to Linode hoping that this would speed things up. But nothing happened.

Saturday morning the problem cropped up again.

As an immediate fix we changed the A record in the Linode console and it took forever to propagate. So there was a time when the traffic was falling on two servers. One Linode and another one our old server.

This was an issue but in a way it solved the problem as the traffic was now split. Both the servers were now pointing to the DB which was with Linode.

During this period the support from Linode was very bad. They did not deal this as a high priority issue. They were too casual and took their own sweet time to respond.

We had enough and did not want to take any more risk as our customers were getting really frustrated.

We did not have time for Linode to take all the time in the world to troubleshoot this issue as this was about our livelihood and survival.

On Sunday night we migrated out of Linode and things have been good.

A real bad experience and really disappointed.

Thanks for taking the time and effort to share your experience with us, @ks_007 — we truly appreciate it. I've shared your feedback with the company, and we're looking closely at how we handled your issues for lessons on improving our approach in the future.

I want to focus on this sentiment in particular:

We did not have time for Linode to take all the time in the world to troubleshoot this issue as this was about our livelihood and survival.

While reviewing your case with our team today, I'm going to focus on this sentiment to help keep us attuned to the fact that many of our customers' livelihoods depend on consistent quality of service and support from us.

If you have any other thoughts, questions, or concerns, please don't hesitate to share them.

@bbigger Thank you for understanding that sentiment.