htop explained

For the longest time I did not know what everything meant in htop.

I knew that load average 1.0 on my two core machine means that the CPU usage is at 50%. But why does it say 1.0?

I decided to look everything up and document it here.

They also say that the best way to learn something is to try to teach it.

Table of Contents
htop on Ubuntu Server 16.04 x64

Here is a screenshot of htop that I am going to describe.

Screenshot of htop

Uptime

Uptime shows how long the system has been running.

You can see the same information by running uptime:

$ uptime
 12:17:58 up 111 days, 31 min,  1 user,  load average: 0.00, 0.01, 0.05

How does the uptime program know that?

It reads the information from the file /proc/uptime.

9592411.58 9566042.33

The first number is the total number of seconds the system has been up. The second number is how much of that time the machine has spent idle, in seconds

Source: htop explained

The Need to Read

Reading books remains one of the best ways to engage with the world, become a better person and understand life’s questions, big and small.

We all ask each other a lot of questions. But we should all ask one question a lot more often: “What are you reading?”

It’s a simple question but a powerful one, and it can change lives.

Source: The Need to Read – WSJ

List of Computer Science courses with video lectures.

Table of Contents

Source: cs-video-courses/README.md at master · Developer-Y/cs-video-courses · GitHub

$15 Production Kubernetes Cluster on DigitalOcean

As you might already know, I’m into containers, static configuration and self-service infrastructures. Naturally, I love Kubernetes, which I consider the most promising cluster scheduler around.

In fact, the biggest reason to use containers is that they make it possible for something like Kubernetes to operate your cluster. Cluster scheduler like Kubernetes, Mesos or Swarm take care of deploying and moving your applications around without requiring an Operator to allocate resources and redeploy services manually.

Cluster schedulers are here to stay. They will become as ubiquitous as version control and getting experience with it is something I can encourage everyone in the DevOps world to do. Especially if your job is mainly operating. Chances are, your job gets automated.

Source: $15 Production Kubernetes Cluster on DigitalOcean

The Simple Economics of Machine Intelligence

All human activities can be described by five high-level components: data, prediction, judgment, action, and outcomes. For example, a visit to the doctor in response to pain leads to: 1) x-rays, blood tests, monitoring (data), 2) diagnosis of the problem, such as “if we administer treatment A, then we predict outcome X, but if we administer treatment B, then we predict outcome Y” (prediction), 3) weighing options: “given your age, lifestyle, and family status, I think you might be best with treatment A; let’s discuss how you feel about the risks and side effects” (judgment); 4) administering treatment A (action), and 5) full recovery with minor side effects (outcome).

Source: The Simple Economics of Machine Intelligence