munetoshi

Code readability presentation links

English version

• Session 1: Introduction and Principles - https://speakerdeck.com/munetoshi/code-readability-session-1-ver-2-en
• Session 2: Naming - https://speakerdeck.com/munetoshi/code-readability-session-2-ver-2-en
• Session 3: Comments - https://speakerdeck.com/munetoshi/code-readability-session-3-ver-2-en
• Session 4: State - https://speakerdeck.com/munetoshi/code-readability-session-4-ver-2-en
• Session 5: Function - https://speakerdeck.com/munetoshi/code-readability-session-5-ver-2-en
• Session 6: Dependency I - https://speakerdeck.com/munetoshi/code-readability-session-6-ver-2-en

max-rocket-internet

CPU: percentage of limit

A lot of people land when trying to find out how to calculate CPU usage metric correctly in prometheus, myself included! So I'll post what I eventually ended up using as I think it's still a little difficult trying to tie together all the snippets of info here and elsewhere.

This is specific to k8s and containers that have CPU limits set.

To show CPU usage as a percentage of the limit given to the container, this is the Prometheus query we used to create nice graphs in Grafana:

sum(rate(container_cpu_usage_seconds_total{name!~".*prometheus.*", image!="", container_name!="POD"}[5m])) by (pod_name, container_name) /

mitsuruog

express実践入門

---

自己紹介

小川充

• mitsuruog

kenjiskywalker

http://nginx.org/en/docs/http/configuring_https_servers.html
http://nginx.org/ja/docs/http/configuring_https_servers.html

default_server

default_serverは対象のポートに対して有効だから
下記のようにポート毎にデフォルトサーバを指定できる。

server {

Gab-km

GitHub Flow

• Scott Chacon on the Interwebs(リンク切れ)
• Scott Chacon on the Interwebs
• GitHub Flow - The best way to use Git and GitHub

31 Aug 2011

git-flowの問題点 (Issues with git-flow)

jboner

Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference                           0.5 ns
Branch mispredict                            5   ns
L2 cache reference                           7   ns                      14x L1 cache
Mutex lock/unlock                           25   ns
Main memory reference                      100   ns                      20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy             3,000   ns        3 us
Send 1K bytes over 1 Gbps network       10,000   ns       10 us
Read 4K randomly from SSD*             150,000   ns      150 us          ~1GB/sec SSD