Glossary:
- md: multiple devices
| command | description |
|---|---|
cat /proc/mdstat |
show status of all raids |
mdadm --detail /dev/md0 |
detailed status of raid md0 |
| # The path to store the cache files, limit the folder to 100MB | |
| fastcgi_cache_path /var/run/nginx-cache levels=1:2 keys_zone=WORDPRESS:100m; | |
| # A unique request is defined by this cache key | |
| fastcgi_cache_key "$scheme$request_method$host$request_uri"; | |
| # Show the cached version if upstream gives a timeout or a HTTP 500 error | |
| fastcgi_cache_use_stale error timeout invalid_header http_500; | |
| # Don't use the following headers to define the cache variables |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| [plexmediaserver] | |
| title=Plex Media Server | |
| description=The Plex Media Server is smart software that makes playing Movies, TV Shows and other media on your computer simple | |
| ports=32400/tcp|1900/udp|32469/udp|5353/udp |
| .highlight { background-color: #49483e } | |
| .c { color: #75715e } /* Comment */ | |
| .err { color: #960050; background-color: #1e0010 } /* Error */ | |
| .k { color: #66d9ef } /* Keyword */ | |
| .l { color: #ae81ff } /* Literal */ | |
| .n { color: #f8f8f2 } /* Name */ | |
| .o { color: #f92672 } /* Operator */ | |
| .p { color: #f8f8f2 } /* Punctuation */ | |
| .cm { color: #75715e } /* Comment.Multiline */ | |
| .cp { color: #75715e } /* Comment.Preproc */ |