Skip to content




Block or Report

Block or report andrewlouis93

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse


  1. SOCKS4 Public

    🧦 🧦 🧦 🧦

    Go 1

  2. netaddr Public

    Forked from inetaf/netaddr

    Network address types


  3. NGINX Ingress Controller for Kubernetes

    Go 12.7k 6.5k

  4. crypto Public

    Forked from golang/crypto

    [mirror] Go supplementary cryptography libraries


  5. 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.
    ![Older UMA Layout](
    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. 1
    ### How are partitions assigned in a consumer group?
    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.
    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.

939 contributions in the last year

May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Mon Wed Fri

Contribution activity

May 2022

93 contributions in private repositories May 6 – May 24

Seeing something unexpected? Take a look at the GitHub profile guide.