(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
# The next line updates PATH for the Google Cloud SDK. | |
source /Users/dwchiang/google-cloud-sdk/path.zsh.inc | |
# The next line enables zsh completion for gcloud. | |
source /Users/dwchiang/google-cloud-sdk/completion.zsh.inc |
chore: add Oyster build script | |
docs: explain hat wobble | |
feat: add beta sequence | |
fix: remove broken confirmation message | |
refactor: share logic between 4d3d3d3 and flarhgunnstow | |
style: convert tabs to spaces | |
test: ensure Tayne retains clothing |
Moved to git repository: https://github.com/denji/nginx-tuning
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.
#!/bin/sh | |
### BEGIN INIT INFO | |
# Provides: btsync | |
# Required-Start: $local_fs $remote_fs | |
# Required-Stop: $local_fs $remote_fs | |
# Should-Start: $network | |
# Should-Stop: $network | |
# Default-Start: 2 3 4 5 | |
# Default-Stop: 0 1 6 | |
# Short-Description: Multi-user daemonized version of btsync. |