Pinned Loading

1. SOCKS4 SOCKS4 Public

   🧦 🧦 🧦 🧦

   Go

2. netaddr netaddr Public

   Forked from inetaf/netaddr

   Network address types

   Go

3. kubernetes/ingress-nginx kubernetes/ingress-nginx Public

   Ingress NGINX Controller for Kubernetes

   Go 17.7k 8.3k

4. crypto crypto Public

   Forked from golang/crypto

   [mirror] Go supplementary cryptography libraries

   Go

5. What is NUMA, and why should Kuberne... What is NUMA, and why should Kubernetes users care?

   1

   Historically, all memory on x86 architectures were equally accessibly by all CPUs on the system. This is an effective implementation, but there's increased bandwidth on the bus, and the more CPUs you have, the further away from the memory  it is. This layout is called Uniform Memory Access.

   2

   3

   ![Older UMA Layout](http://frankdenneman.nl/wp-content/uploads/2016/07/02-01-System_Bus.png)

   4

   5

   Modern x86 architectures introuduce the concept of memory nodes (also referred to elsewhere as zones or cells), where new writes are associated with a CPU's memory node. The nodes are connected by a bus, so all the memory is still accessible via any CPU, but of course, we have faster memory access time for CPUs accessing local nodes.

6. Kafka: Notes on Consuming from Multi... Kafka: Notes on Consuming from Multiple Topics

   1

   ### How are partitions assigned in a consumer group?

   2

   3

   This is based on the [partition assignment strategy]() configuration, an important note here is that this is a topic-specific configuration. It can only be used to describe the strategy used to assign partitions to a specific consumer group.

   4

   5

   The default strategy is called the `RangeAssignor` strategy. In this strategy, we divide the number of partitions over the number of consumer instances, and assign one by one. If the division does not result in a nice round number, the first few consumer instances are assigned more partitions.