Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
25% Recurring Discount on NVMe VPS
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
CloudLinux
Shells Virtual Desktop
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.

How big VPS for 200k PHP requests / hour on peak time?

but almost idle otherwise.

Cannot be cached other than with cloudflare.

Comments

  • omelasomelas Member
    edited March 2018

    It that a course registration system for a university?

  • stefemanstefeman Member
    edited March 2018

    @omelas said:
    It that a course registration system for a university?

    No, its a reader for single scanlation group that translates unlisenced work. And we get tons of scrapers on release.

  • No one can answer this except you.

    Entirely depends on resources used per request. If each request is just a file_get_contents, you could pull that off on a tiny server... if each request is requiring several expensive calculations like gd/imagemagick or for loops over large arrays, you're going to have a much different experience

    You would need to determine this number yourself by calculating the average resource usage per request and extrapolating... you could also just go larger than you think you'll need, then scale down after testing it once.

Sign In or Register to comment.