Harry P
New member
- Joined
- Feb 3, 2015
- Messages
- 347
- Points
- 0
I keep running into people who moved to a VPS because a forum told them shared hosting was holding the site back, then spent six months learning server administration they did not need for a site doing four hundred visits a day.
The moves that looked genuinely necessary were nearly always about one specific limit rather than performance in general. Hitting the process or memory cap during traffic spikes and getting 508s. Needing a PHP extension or a cron frequency the host would not enable. A neighbour on the same IP getting the range listed and your outgoing mail landing in spam. Wanting root because something you had to run was never going to work through a panel.
The moves that looked premature were almost always someone chasing a page speed score that turned out to be an unoptimised image and a plugin doing far too many queries. Same code on a faster server is still the same code.
So what pushed you over in the end, and did it fix the thing you expected it to? I am curious how many people got there and found the real bottleneck was somewhere else entirely.
The moves that looked genuinely necessary were nearly always about one specific limit rather than performance in general. Hitting the process or memory cap during traffic spikes and getting 508s. Needing a PHP extension or a cron frequency the host would not enable. A neighbour on the same IP getting the range listed and your outgoing mail landing in spam. Wanting root because something you had to run was never going to work through a panel.
The moves that looked premature were almost always someone chasing a page speed score that turned out to be an unoptimised image and a plugin doing far too many queries. Same code on a faster server is still the same code.
So what pushed you over in the end, and did it fix the thing you expected it to? I am curious how many people got there and found the real bottleneck was somewhere else entirely.
