3 ms·

Node does not prioritize performance. vCPUs don't prioritize or guarantee performance. 2GB physical ram may not be a lot. 1Mb bandwidth (~100KBytes/s) may no

Node does not prioritize performance. vCPUs don't prioritize or guarantee performance. 2GB physical ram may not be a lot. 1Mb bandwidth (~100KBytes/s) may not be a lot if multiple simultaneous users with bulk payloads. Storage may not be performant. Personally as a first step I would just migrate it to a better, dedicated server. Consider the cost of your time to research it. In the West a midrange older dedicated server starts at ~US$30/mo. All kinds of potential badness about being in a vm on a shared resource are eliminated. If not, or if that doesn't buy you a solution, you must characterize which of the vserver itself, cpu, storage, or bandwidth is the bottleneck. Assuming it's linux, I would ssh in and set up prometheus or similar monitoring so you can see it over a week. If no problem, hit it with concurrent transactions until there is a problem. Compare what you have to do to see a problem on a setup on your laptop vs the remote server, you can judge your vserver then. For cpu, look with top how it acts when you give it transactions. Who eats cpu? Memory, top + vmstat. For storage, iostat. Network, netstat -s

viraptor 5y ago
> Personally as a first step I would just migrate it to a better, dedicated server. Consider the cost of your time to research it. I strongly believe that's a terrible idea as the first step. It may be a solution once you know the reason for the slowdown, but if it's something trivial like a lack of database index, or an accidentally quadradic algorithm, you'll just run into the same issue on a bigger host in a few days with more traffic.
- fivelessminutes 5y ago
  I understand that POV, but if you're on the cheapest possible vcpus, gaining a difficult-to-acquire deep understanding of how overcommitted they are and how sporadically unusable it is as a platform is not worth anything. Sure it's the wrong move to blow $2K/mo on some Xeon, but it's not the wrong move to spend $30 on bracketing the extent of the platform's problems.
pototo666 5y ago
Thanks sir :)

viraptor 5y ago

> Personally as a first step I would just migrate it to a better, dedicated server. Consider the cost of your time to research it. I strongly believe that's a terrible idea as the first step. It may be a solution once you know the reason for the slowdown, but if it's something trivial like a lack of database index, or an accidentally quadradic algorithm, you'll just run into the same issue on a bigger host in a few days with more traffic.

fivelessminutes 5y ago
I understand that POV, but if you're on the cheapest possible vcpus, gaining a difficult-to-acquire deep understanding of how overcommitted they are and how sporadically unusable it is as a platform is not worth anything. Sure it's the wrong move to blow $2K/mo on some Xeon, but it's not the wrong move to spend $30 on bracketing the extent of the platform's problems.

pototo666 5y ago

Thanks sir :)