How much traffic can handle this dedicate server?

[iulianalex]

Hello guys
What traffic can handle an dedicate server 16 GB RAM , if with 30k visits in 7 days i consume 15 gb bandwidth?

 

[SharkServers]

You can't tell that using these values. How much a server can handle depends on far more than just RAM. Even if you told us what CPU this has, it would not be enough.

It also depends on things like:

• the type of script(s) you run (a small, but badly written script can crash the web server easily);
• what storage the server has (HDD/SSD/etc)
• the amount of visits per second
• Server software configuration
• lots of other things

The only way to tell is to test is to actually benchmark the server and/or run the site and see for yourself, although 30k visits over 7 days should be possible with nearly any server on the market these days provided your scripts are not buggy.

 

[Darmor]

Like @SharkServers said, it depends on a ton of factors, but with 1 visit every 20 seconds or so average, you're good for a while unless your software is really bad.

To have some sort of comparison to with with, a 5 dollar VPS easily handles 100-150 visits per second with the average optimized WordPress installation, given that it has access to a 1,000mbps uplink.

(yes, that's a huge number, but I've worked with 5 dollar VPSes handling 30-40 milion requests per week)

With extremely optimized enterprise-grade software, it's not uncommon to see 10-20k requests per second handled by a single dedicated server.

 

[lancis]

To have some sort of comparison to with with, a 5 dollar VPS easily handles 100-150 visits per second with the average optimized WordPress installation, given that it has access to a 1,000mbps uplink.

What you did to achieve these numbers with WP? Its a major resource hog.

In my tests with apache bench, 5 dollar VPS with Wordpress can handle ~3 requests/sec.
Fully optimized VPS with thin content and fast WP theme can reach ~5 requests/sec.

Just to compare Node.js application per same VPS spec reaches ~700 requests/sec.
Static content is somewhere near ~2000 requests/sec.

 

[Darmor]

What you did to achieve these numbers with WP? Its a major resource hog.

In my tests with apache bench, 5 dollar VPS with Wordpress can handle ~3 requests/sec.
Fully optimized VPS with thin content and fast WP theme can reach ~5 requests/sec.

Just to compare Node.js application per same VPS spec reaches ~700 requests/sec.
Static content is somewhere near ~2000 requests/sec.

- Offload all static resources to a CDN (the usual leech from google/maxcdn/etc)
- Leech imgur for all images (you can quickly make scripts that post all images you upload to WP to imgur instead, and check every now and then for them being still live and re-upload when/if they go down)
- Install, optimize an nginx + mariadb + php-fpm stack manually via ssh (so your VPS is as minimal as it gets, no phpMyAdmin, CPanel, etc)
- Use a Redis cache, so the page is rendered only on the first visit to it, then loaded from Redis on every consecutive visit (not a WP plugin or any of that shit tho, use the NGINX HTTP Redis caching module)

I say "average" optimized because this is doable within a 15-30min installation after following a few decent tutorials here and there (and is basically the checklist every page speed tool out there presents).

If you want to go the extra mile, putting yourself behind CloudFlare, leveraging their caching layer and RocketLoader (I think that was the name for their JS optimizer), you can actually match Node's performance

 

[iulianalex]

You can't tell that using these values. How much a server can handle depends on far more than just RAM. Even if you told us what CPU this has, it would not be enough.

It also depends on things like:

• the type of script(s) you run (a small, but badly written script can crash the web server easily);
• what storage the server has (HDD/SSD/etc)
• the amount of visits per second
• Server software configuration
• lots of other things

The only way to tell is to test is to actually benchmark the server and/or run the site and see for yourself, although 30k visits over 7 days should be possible with nearly any server on the market these days provided your scripts are not buggy.

Actually the dedicate server i buyed from you yesterday , is the 70$ one ..still waithing to be ready.
I want an estimative prognoze that i gues for experience people can tell what to expect
Becouse i expect to increase traffic and dont want in some point to have surprise.
30k visits , 7 days , 15 gb bandwith , traffic spread for all day ....i want to know aprox how much traffic can handle without problems , loads etc

 

[SharkServers]

Actually the dedicate server i buyed from you yesterday , is the 70$ one ..still waithing to be ready.
I want an estimative prognoze that i gues for experience people can tell what to expect
Becouse i expect to increase traffic and dont want in some point to have surprise.
30k visits , 7 days , 15 gb bandwith , traffic spread for all day ....i want to know aprox how much traffic can handle without problems , loads etc

The provisioning will be done by Monday morning (UK time), as we're awaiting a few components to be delivered. As for traffic, again - you can't tell without testing, as there are far too many variables. As I said, a buggy script can crash most powerful servers, while a well configured script would perform well even on low-end boxes.

 

[bobojonathan]

This thread is really an eye opener. Didn't know that i need to optimize VPS's to improve its performance.

 

[lancis]

- Offload all static resources to a CDN (the usual leech from google/maxcdn/etc)
- Leech imgur for all images (you can quickly make scripts that post all images you upload to WP to imgur instead, and check every now and then for them being still live and re-upload when/if they go down)
- Install, optimize an nginx + mariadb + php-fpm stack manually via ssh (so your VPS is as minimal as it gets, no phpMyAdmin, CPanel, etc)
- Use a Redis cache, so the page is rendered only on the first visit to it, then loaded from Redis on every consecutive visit (not a WP plugin or any of that shit tho, use the NGINX HTTP Redis caching module)

I say "average" optimized because this is doable within a 15-30min installation after following a few decent tutorials here and there (and is basically the checklist every page speed tool out there presents).

If you want to go the extra mile, putting yourself behind CloudFlare, leveraging their caching layer and RocketLoader (I think that was the name for their JS optimizer), you can actually match Node's performance

Ahh, Redis cache is what does the difference, I thought you were serving 150 request/sec with pure PHP.
By the way, with Nginx built-in cache you can probably increase that number to 600-1000 requests/sec.

 

[Darmor]

Ahh, Redis cache is what does the difference, I thought you were serving 150 request/sec with pure PHP.
By the way, with Nginx built-in cache you can probably increase that number to 600-1000 requests/sec.

Honestly I'm only fiddling with WP when helping out friends with their PBNs. Otherwise I'm all about Go these days, pushing the limits far above WP/Node

 

[lancis]

Honestly I'm only fiddling with WP when helping out friends with their PBNs. Otherwise I'm all about Go these days, pushing the limits far above WP/Node

This is pretty impressive: https://benchmarksgame.alioth.debian.org/u64q/compare.php?lang=go&lang2=node
Whats the secret sauce of Go?

 

[skorbin]

run some tests on it so that you can then do some math on scaling up and seeing what you can handle. get ready to have your server provider upgrade when you need more capabilities

 

[Darmor]

Whats the secret sauce of Go?

It's basically C with a garbage collector It's just really close to the hardware, and really good at concurrency with it's lightweight thread model (goroutines)

 

[WootHosting]

Sometimes it’s more than RAM, we’d need CPU and HDD/SSD too, in order to base any of this off. I’d recommend starting up from the bottom and working up, slowly.