Diogo Gomes gomes

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

Technology

Vagas para atuação com Java na TecSinapse

Migrado para o site: http://tecsinapse.com.br/nossas-vagas

Rust developer tools - status and strategy

Availability and quality of developer tools are an important factor in the success of a programming language. C/C++ has remained dominant in the systems space in part because of the huge number of tools tailored to these lanaguages. Succesful modern languages have had excellent tool support (Java in particular, Scala, Javascript, etc.). Finally, LLVM has been successful in part because it is much easier to extend than GCC. So far, Rust has done pretty well with developer tools, we have a compiler which produces good quality code in reasonable time, good support for debug symbols which lets us leverage C++/lanaguge agnostic tools such as debuggers, profilers, etc., there are also syntax highlighting, cross-reference, code completion, and documentation tools.

In this document I want to layout what Rust tools exist and where to find them, highlight opportunities for tool developement in the short and long term, and start a discussion about where to focus our time an

	# Kernel sysctl configuration file for Red Hat Linux
	#
	# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
	# sysctl.conf(5) for more details.

	# Controls source route verification
	net.ipv4.conf.default.rp_filter = 1

	# Do not accept source routing
	net.ipv4.conf.default.accept_source_route = 0

	#!/usr/bin/env sh

	##
	# This is script with usefull tips taken from:
	# https://github.com/mathiasbynens/dotfiles/blob/master/.osx
	#
	# install it:
	# curl -sL https://raw.github.com/gist/2108403/hack.sh \| sh
	#

	#!/usr/bin/env ruby
	#
	# this is a special meta-check. It runs ping checks against all hosts in
	# the /endpoints API and sends individual results directly to sensu-client via
	# the udp/3030 client socket. this is different from the normal sensu check model
	# where individual scripts run and their exit status and output is used to create
	# a single event.
	#
	# the reason for this check is to be able to dynamically ping a list of hosts
	# without the race conditions and timing issues involved with creating individual

	#! /usr/bin/perl

	$stage = 1;

	while (<STDIN>) {
	if ($stage == 1) {
	if (/TRACE (\d+)/) {
	if ($line ne '') {
	$cpu{$id} = $line;
	}

Diogo Gomes gomes

Benchmarking Nginx with Go

Technology

Vagas para atuação com Java na TecSinapse

Rust developer tools - status and strategy

Contents