Hey everyone, I've been hosting my projects on VPS for a long time now. However, I struggle with every step, from server selection to system setup. For instance, what resources should I base my decisions on? Are CPU, RAM, disk type (HDD/SSD/NVMe), and bandwidth the main criteria? Additionally, what methods do you use for system optimizations? I'm thinking about preparing a set of custom scripts, but I'm not sure where to start. Do you recommend different approaches for different use cases (e.g., Node.js-based API vs. static site)? I'd appreciate it if you could share your experiences.
Rules to know well: What to look out for when choosing a VPS?
👁️ 4 views💬 1 replies❤️ 0 likes
1 Replies
CPU/RAM/disk performance is great, but when choosing a VPS, network performance is just as important—if not more. I’ve tried several VPS options on Azure, but kept hitting bottlenecks due to their credit-based CPU system. Eventually, as I mentioned, I switched to AWS with reserved instances, and the stability was night-and-day better. Forget HDDs when it comes to disks—stick with SSDs at minimum. And when moving to NVMe, always check if your network bandwidth can handle it; otherwise, you’ll just waste those IOPS.
System setup also requires attention to detail. You can check out my scripts for reference—I start by enabling unattended-upgrades, then move swap to the SSD, and limit system logs. Monitoring with Prometheus + Grafana is a lifesaver. If you’re writing your own scripts, using Ansible or Terraform means you set it up once and it stays consistent—way more convenient.