kriskornel

Moved to git-repository: https://github.com/denji/awesome-http-benchmark

Tools

Located in alphabetical order (not prefer)

• ab – slow and single threaded, written in C
• apib – most of the features of ApacheBench (ab), also designed as a more modern replacement, written in C
• baloo – Expressive end-to-end HTTP API testing made easy, written in Go (golang)
• bombardier – Fast crossplatform HTTP benchmarking tool, written in Go (golang)

kriskornel

Moved to git-repository: https://github.com/denji/awesome-http-benchmark

Tools

Located in alphabetical order (not prefer)

• ab – slow and single threaded, written in C
• apib – most of the features of ApacheBench (ab), also designed as a more modern replacement, written in C
• baloo – Expressive end-to-end HTTP API testing made easy, written in Go (golang)
• bombardier – Fast crossplatform HTTP benchmarking tool, written in Go (golang)

kriskornel

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

• Go HTTP standalone (as the control group)
• Nginx proxy to Go HTTP
• Nginx fastcgi to Go TCP FastCGI
• Nginx fastcgi to Go Unix Socket FastCGI

kriskornel

www.mysite.com, mysite.com {
  proxy / webapp:3000 {
    proxy_header Host {host}
    proxy_header X-Real-IP {remote}
    proxy_header X-Forwarded-Proto {scheme}
  }
  gzip
  tls [email protected]
}

kriskornel

root@deikxyz:~# cat /dev/null >  cat /dev/null > /var/log/nginx/access.log
(hit enter)
root@deikxyz:~# cat /dev/null >  cat /dev/null > /var/log/nginx/error.log
(hit enter)

kriskornel

window.App = new Vue({
		el: '#app',
		data: {
			low: 0,
			median: 0,
			high: 0,		
			duration: 0,	
			lecture_duration: [],
			weekdays: {
				mon: [],

kriskornel

window.App = new Vue({
		el: '#app',
		data: {
			low: 0,
			median: 0,
			high: 0,		
			duration: 0,	
			lecture_duration: [],
			weekdays: {
				mon: [],

kriskornel

window.App = new Vue({
		el: '#app',
		data: {
			low: 0,
			median: 0,
			high: 0,		
			duration: 0,	
			lecture_duration: [],
			weekdays: {
				mon: [],

kriskornel

window.App = new Vue({
		el: '#app',
		data: {
			low: 0,
			median: 0,
			high: 0,		
			duration: 0,	
			lecture_duration: [],
			weekdays: {
				mon: [],

kriskornel

# Langkah-langkah untuk Merge Ke Production:
--

## Contents:
--
1. Bitbucket
   - Merge dari branch dev ke master (lakukan melalui bitbucket)
   - Masuk ke Server lakukan pull request untuk coding terbaru:
     ```git pull origin master```