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
ReliableSite White-Label Dedicated Hosting for Resellers
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
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 many hits can your site take?

I have been playing around with blitz.io today. The free trial is pretty cool (10 free credits). I tested it against my cached wordpress.

1-4000 2000ms timeout https://www.blitz.io/report/9c646312e6c614adfd77aa176e779e15#/
1-1000 5000ms timeout www.blitz.io/report/9c646312e6c614adfd77aa176eb60d54

I thought 160140522 hits/day was nice for a 1GB VPS for ~$4 a month :D

What do you guys get? :-)

Comments

  • You know it depends on many factors.
    Like: CPU, Internet Channel Speed, Latency, Cached or nope website, Memory, Web-server, kernel etc.

    There is no really hard to make full cached most popular CMS.

    Try better to make ab/siege/blitz test on the IP Boards. Interesting how much it will show.

    Anyway, we can easy calculate the maximum possible hits per day by very simple formula:
    ( (Internet Bandwidth/Cached Page Size) * - ( Architecture mistakes (CPU/Disk IO/Memory/Latency) ) * 24 hours in seconds )

    Sorry for the nerd mod.
    Anyway, you have awesome result.
    What are you using, Varnish i guess? + W3 Cache Plugin?

  • @neqste said:
    You know it depends on many factors.
    Like: CPU, Internet Channel Speed, Latency, Cached or nope website, Memory, Web-server, kernel etc.

    There is no really hard to make full cached most popular CMS.

    Try better to make ab/siege/blitz test on the IP Boards. Interesting how much it will show.

    Anyway, we can easy calculate the maximum possible hits per day by very simple formula:
    ( (Internet Bandwidth/Cached Page Size) * - ( Architecture mistakes (CPU/Disk IO/Memory/Latency) ) * 24 hours in seconds )

    Sorry for the nerd mod.
    Anyway, you have awesome result.
    What are you using, Varnish i guess? + W3 Cache Plugin?

    Units please?

  • @neqste said:
    You know it depends on many factors.
    Like: CPU, Internet Channel Speed, Latency, Cached or nope website, Memory, Web-server, kernel etc.

    There is no really hard to make full cached most popular CMS.

    Try better to make ab/siege/blitz test on the IP Boards. Interesting how much it will show.

    Anyway, we can easy calculate the maximum possible hits per day by very simple formula:
    ( (Internet Bandwidth/Cached Page Size) * - ( Architecture mistakes (CPU/Disk IO/Memory/Latency) ) * 24 hours in seconds )

    Sorry for the nerd mod.
    Anyway, you have awesome result.
    What are you using, Varnish i guess? + W3 Cache Plugin?

    I'm using Nginx Fastcgi cache in RAM. Simple and effective :-)

  • @salmon said:
    I'm using Nginx Fastcgi cache in RAM. Simple and effective :-)

    very interesting, can i check few strings of fastcgi_cache from your config?
    because maybe i am false somewhere.

  • @neqste I used the tutorial found here: https://rtcamp.com/wordpress-nginx/tutorials/single-site/fastcgi-cache-with-purging/

    `set $skip_cache 0;

    # POST requests and urls with a query string should always go to PHP
    if ($request_method = POST) {
        set $skip_cache 1;
    }   
    if ($query_string != "") {
        set $skip_cache 1;
    }   
    
    # Don't cache uris containing the following segments
    if ($request_uri ~* "/wp-admin/|/xmlrpc.php|wp-.*.php|/feed/|index.php|sitemap(_index)?.xml") {
        set $skip_cache 1;
    }   
    
    # Don't use the cache for logged in users or recent commenters
    if ($http_cookie ~* "comment_author|wordpress_[a-f0-9]+|wp-postpass|wordpress_no_cache|wordpress_logged_in") {
        set $skip_cache 1;
    }
    
    location / {
        try_files $uri $uri/ /index.php?$args;
    }    
    
    location ~ .php$ {
        try_files $uri /index.php; 
        include fastcgi_params;
        fastcgi_pass unix:/var/run/php5-fpm.sock;
    
        fastcgi_cache_bypass $skip_cache;
            fastcgi_no_cache $skip_cache;
    
        fastcgi_cache TOMWORDPRESS;
        fastcgi_cache_valid  60m;
    }
    
    location ~ /purge(/.*) {
        fastcgi_cache_purge TOMWORDPRESS "$scheme$request_method$host$1";
    }   
    
    location ~* ^.+\.(ogg|ogv|svg|svgz|eot|otf|woff|mp4|ttf|rss|atom|jpg|jpeg|gif|png|ico|zip|tgz|gz|rar|bz2|doc|xls|exe|ppt|tar|mid|midi|wav|bmp|rtf)$ {
        access_log off; log_not_found off; expires max;
    }
    
    location = /robots.txt { access_log off; log_not_found off; }
    location ~ /\. { deny  all; access_log off; log_not_found off; }
    

    `

  • NeoonNeoon Community Contributor, Veteran
    edited January 2014

    I justed tested it on a normal lighttpd with cgi and mybb, after 404 hits the server died.
    Ok it was only 96MB <3

  • @Infinity580 said:
    I justed tested it on a normal lighttpd with cgi and mybb, after 404 hits the server died.
    Ok it was only 96MB <3

    Oh no, RIP little server you never stood a chance in life ;(

Sign In or Register to comment.