Sets system time based on what is reported by google.com. Useful for cases where it is not possible to use the standard ntpdate command. For eample, if a Linux machine is on a network which is only able to reach the internet through an HTTP proxy.
Inspired by ryenus' answer @ https://superuser.com/a/807326/72342
# Download latest set_system_clock_from_google.sh script.
| For REST/JSON web service that returns : | |
| { | |
| "DatabaseConnections": [ | |
| { | |
| "DatabaseName": "database1", | |
| "DatabaseStatus": "Open", | |
| }, | |
| { | |
| "DatabaseName": "database2", | |
| "DatabaseStatus": "Open", |
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.
| [mysqld_safe] | |
| nice = -15 | |
| [mysqld] | |
| max_binlog_size = 256M #max size for binlog before rolling | |
| expire_logs_days = 1 #binlog files older than this will be purged | |
| ## Per-Thread Buffers * (max_connections) = total per-thread mem usage | |
| thread_stack = 256K #default: 32bit: 192K, 64bit: 256K | |
| sort_buffer_size = 1M #default: 2M, larger may cause perf issues |
This gist assumes: